CATO*.DLL problem
in [Visual Objects]
|
Prev: CDX numeric Seek (old problem?)
Next: CATO*.DLL BUG
From: Alessandro Antonangeli on 21 Jan 2010 15:11 > Just a thought but could you put a dummy call to one of the functions in > CATO...DLL in your app to make sure it gets linked in properly. > Something similar to making a call to DELETED() in your program to > ensure its visible and included so you can use it in your indexes. > > Maybe the functions from CATO DLL are only called by one of the other VO > DLLs and thats why you dont get an error about missing DLL. This may > also be rubbish! > > HTH > > Simon > I will try tomorrow -- Ciao, Alessandro
From: Geoff Schaller on 23 Jan 2010 20:31 Alessandro. I've just read through the thread and something is not quite right. For instance, I do not use any CATO*.dll except for the SplitWindow DLL and as far as I know, none of the others are relevant to editing unless you are referring to the databrowser dll. Even so, this is NOT an association problem. It cannot be because that is not what Association is about - it is about registering file extension with an application and causing some action based on what you do with it. Secondly, the application must run and find the DLL if it is in the exe folder and this will be irrespective of paths set in the application. It cannot fail. If it fails then you need to look for something environmental such as launching your exe from one location and specifying another as the "Start In" or if you are relying on paths, then the wrong version is being found. Look to Paths. What are they? Normally you should remove ALL paths set and rely totally on the exe folder for dll locations. You cannot associate a DLL with a path they way you seem to be suggesting. Geoff "Alessandro Antonangeli" <alcati.r3m0v3th1s(a)alcati.com> wrote in message news:hj7h0n$qs9$1(a)speranza.aioe.org: > Hi all > > I did a little application to browse and modify DB. Tested on a dir where > all DLL are present, it's fine than I put in the right dir, but without > CATO* dll > It work without any problem except the fact I cannot edit field, just > see. No complaining for the absence. > > After a little I found it was this the problem and ok, but ... I did > associated the application to my DBF so that it should be automatically > started if i double click on one of them and open the DBF. It works: but > still in read only: cannot modify fields. > > So if I start from the dir where the exe is, all fine, otherwise CATO* > are not seen and not used. > > I've been missing something or it is a bug/problem? > > -- > Ciao, Alessandro
From: Alessandro Antonangeli on 24 Jan 2010 10:46 Il Thu, 21 Jan 2010 18:57:18 +0000, Simon Goodman ha scritto: > Hi Alessandro, > > Just a thought but could you put a dummy call to one of the functions in > CATO...DLL in your app to make sure it gets linked in properly. > Something similar to making a call to DELETED() in your program to > ensure its visible and included so you can use it in your indexes. No, it doesnt work, thanks anyway -- Ciao, Alessandro
From: Alessandro Antonangeli on 24 Jan 2010 10:58 Il Sun, 24 Jan 2010 01:31:11 +0000, Geoff Schaller ha scritto: > are referring to the databrowser dll. yes > Even so, this is NOT an association problem. It cannot be because that yes, the problem is that the exe is not able to find them in the dir where the exe is (even if they are there) > Secondly, the application must run and find the DLL if it is in the exe > folder and this will be irrespective of paths set in the application. May be you missed something: if I run the exe from the dir where it is, all works fine. If the application is started because a file (*.dbf) is associated with it, the application, the exe, cannot find the CATO* dll (even if they are in the same exe dir) Cavo 2.8 SP 2, WXP If this is not a bug, why the exe works fine if started from its dir and not when is started by double clicking on a dbf file? Or better: how to make it works? -- Ciao, Alessandro
From: Johan Nel on 24 Jan 2010 13:39
Alessandro, If it is opened from clicking on .DBF, then it will start from that folder as the default directory. Do a SET PATH on the folder that you exe is residing in and it should fix the problem I believe... Regards, Johan Nel Pretoria, South Africa. Alessandro Antonangeli wrote: > Il Sun, 24 Jan 2010 01:31:11 +0000, Geoff Schaller ha scritto: > >> are referring to the databrowser dll. > > yes > >> Even so, this is NOT an association problem. It cannot be because that > > yes, the problem is that the exe is not able to find them in the dir > where the exe is (even if they are there) > >> Secondly, the application must run and find the DLL if it is in the exe >> folder and this will be irrespective of paths set in the application. > > May be you missed something: if I run the exe from the dir where it is, > all works fine. > If the application is started because a file (*.dbf) is associated with > it, the application, the exe, cannot find the CATO* dll (even if they are > in the same exe dir) > > Cavo 2.8 SP 2, WXP > > If this is not a bug, why the exe works fine if started from its dir and > not when is started by double clicking on a dbf file? Or better: how to > make it works? > |