Dennis, Javier, Razzak Thanks for the ideas. I would have never looked at the compiled app properties for the fix. More stuff to play with tomorrow to understand it.
Tom Frederick -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Wednesday, January 30, 2013 8:44 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Compiler and CurrDir At 06:29 AM 1/30/2013, Tom Frederick wrote: >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, A few suggestions: 01. Check the shortcut properties of your compiled application executable Target: Start in: 02. Check the .DAT file for compiled project Hope that provides you with some blue's clues ... Very Best R:egards, Razzak. www.rbase.com www.facebook.com/rbase
