CATO*.DLL problem
in [Visual Objects]
|
Prev: CDX numeric Seek (old problem?)
Next: CATO*.DLL BUG
From: Alessandro Antonangeli on 26 Jan 2010 09:37 > You are not paying for bug fixes too. You are paying to keep the product > alive. Yes, but without improvements it is dead anyway. I would pay for improvements, even little: like, for example, the one I proposed some times ago to make the IDE tree of the application deeper, so that one can group. -- Ciao, Alessandro
From: Geoff Schaller on 26 Jan 2010 17:09 Then it should be no problem for you to send me such an aef. Then I know we have the same conditions and options You either want help or you don't - your choice. "Alessandro Antonangeli" <alcati.r3m0v3th1s(a)alcati.com> wrote in message news:hjmjbg$qri$1(a)speranza.aioe.org: > Il Tue, 26 Jan 2010 10:30:39 +0000, Geoff Schaller ha scritto: > > > > Can you email me your sample aef. > > Let us sing from the same song sheet. > > > It's simple, just make a new MDI and put the code I posted Monday 17:47 > in place of START function > > -- > Ciao, Alessandro
From: Geoff Schaller on 26 Jan 2010 17:14 Alessandro, I think you missed the announcement: VO is dead and is now in what could kindly be called 'maintenance mode'. There is no point making any major enhancements because we are all moving on to Dot Net. Everyone ultimately. For "VO" enhancements you should look to Vulcan for that is where GrafX is now placing its efforts. If you don't like the prospect of Vulcan then go to C#. Whilst I am no advocate of Vulcan I will say right here and now that you can EASILY extend your VO application and future proof yourself by adopting VO or Vulcan to move forward with. You cannot move forward on VO alone any more than I see those truly sad clipper types clinging on 16 bit applications. Some folks are locking themselves into the past by adopting xHarbour - the forward thinking ones are adopting Dot net. Move forward Alessandro. Geoff "Alessandro Antonangeli" <alcati.r3m0v3th1s(a)alcati.com> wrote in message news:hjmumf$dp1$1(a)speranza.aioe.org: > > You are not paying for bug fixes too. You are paying to keep the product > > alive. > > > Yes, but without improvements it is dead anyway. > I would pay for improvements, even little: like, for example, the one I > proposed some times ago to make the IDE tree of the application deeper, > so that one can group. > > -- > Ciao, Alessandro
From: Stephen Quinn on 31 Jan 2010 09:48 Alessandro Have you placed the directory where the CATO*.DLLs reside in the SYSTEM and/or USER PATH?? If not then the OS will NEVER find them, unless you put them in C:\WINDOWS\SYSTEM32. Your EXE doesn't need to find them, windows does. Windows searchs 1: current directory (ie where the DBF is, not where the exe is) I may be wrong about the order from here on<bg> 2: windows\system32 (should already be in the PATH) 3: system path 4: ????? CYA Steve
From: Amilcar A. Camargo on 31 Jan 2010 12:38
On Sun, 31 Jan 2010 14:48:51 GMT, "Stephen Quinn" <stevejqNO(a)bigpondSPAM.net.au> wrote: >Alessandro > >Have you placed the directory where the CATO*.DLLs reside in the SYSTEM >and/or USER PATH?? >If not then the OS will NEVER find them, unless you put them in >C:\WINDOWS\SYSTEM32. > >Your EXE doesn't need to find them, windows does. > >Windows searchs > 1: current directory (ie where the DBF is, not where the exe is) > >I may be wrong about the order from here on<bg> > 2: windows\system32 (should already be in the PATH) > 3: system path > 4: ????? You can also specify a 'path' for your app that will be appended to current path uppon execution. In the registry: Under key 'HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths' 1. Add a key with your app exe name: 'yourexe.exe' 2. Add a (default) value with your exe full path 3. Add a 'Path' value with the path(s) that should be searched Look at the various keys in the registry to have an idea. This works very fine. I use it all the time in my setup scripts and works a treat. Some time in the past there were some glitches with this but i have not seen any trouble in the last years. Best regards, Amilcar A. Camargo F. Guatemala, C. A. |