Tom,
I use something just like yours and it works correctly in version 9.1 compiled. The value of "currdir" returns the path of where the application was stared rather than where the target is, as per information on the Windows shortcut. Check your application Windows shortcut and make sure the "Start in:" points to the location where you want to start; if this path is not defined, it defaults to the path of the target application which I believe is your issue. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: [email protected] [mailto:[email protected]] On Behalf Of tfred Sent: Wednesday, January 30, 2013 5:30 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Compiler and CurrDir We make PDFs of all reports and store them in a sub. On our network the database is on Y:\ and the sub is Y:\PDFs\. At home, database is on C:\RBTI\RBG96_64\Samples and the sub C:\RBTI\RBG96_64\Samples\PDFs. I have always used (cval('CurrDir')) to locate the correct database location and store/find the PFDs regardless of the computer. It always works. Lately, this works correctly in uncompiled versions, but when I compile to an .exe file the value of CurrDir is assigned the name of the compiler directory regardless of where the actual .exe is built. We have compiled our system for several years with no problems. I put a screen of variables right after CurrDir is fired and the value of CurrDir was 'C:\RBTI\RBG96_64_Compiler' even when the .exe was built on network Y:\ (work) or C:\ (home). A workaround with ISCOMPILED and an IF..THEN works, but I'd rather have CurrDir adjust to the location of the database as it always has. Any suggestions? Tom Frederick Jacksonville, IL
