Prev: CDX numeric Seek (old problem?)
Next: CATO*.DLL BUG
From: Alessandro Antonangeli on 20 Jan 2010 13:11 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: Willie Moore on 20 Jan 2010 14:03 Alessandro, When you do your association, can you set the start-in to point to the directory where the exe resides? That should fix the issue. Regards, Willie "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 > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4791 (20100120) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4791 (20100120) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Alessandro Antonangeli on 20 Jan 2010 14:23 > When you do your association, can you set the start-in to point to the > directory where the exe resides? That should fix the issue. Hi Willie As far as i know, when you associate a program to a kind of file, you cannot set the directory. You can do with a link, but you cannot associate a lnk as a start for an application. Anyway it wouldnt be a fix, but a workaround ^^ Thanks for your reply -- Ciao, Alessandro
From: Willie Moore on 20 Jan 2010 16:58 Alessandro, I quick workaround would be to put the cato files in a directory that is in the path. Regards, Willie "Alessandro Antonangeli" <alcati.r3m0v3th1s(a)alcati.com> wrote in message news:hj7l6t$1t2$1(a)speranza.aioe.org... >> When you do your association, can you set the start-in to point to the >> directory where the exe resides? That should fix the issue. > > Hi Willie > > As far as i know, when you associate a program to a kind of file, you > cannot set the directory. You can do with a link, but you cannot > associate a lnk as a start for an application. > > Anyway it wouldnt be a fix, but a workaround ^^ > > Thanks for your reply > > > -- > Ciao, Alessandro > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4791 (20100120) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4791 (20100120) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
From: Paul D B on 21 Jan 2010 03:37
Alessandro Antonangeli wrote: > 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? Hi Alessandro, There are plenty of applications doing exactly the same thing and they work (e.g. DB Administrator which, if I recall correctly, was delivered on the VO2.6 CD and I'm still using it every day) . So 1) yes you are missing something and 2) why don't you just use these? PS: have you tried the Workdir() function in your application? It returns the directory associated with the EXE. Then play with Setpath(). -- Paul |