Tom,
If you like to store the PDF's on the network I have found out it is better to use \\ <file:///\\%3cserver_name%3e\PDFs> <server_name>\PDFs If you do this you are sure the PDF is stored at the right place. For instance, if one of the computers is using Z:\ instead of Y:\ for mapping it will go wrong. Another idea could be to store this kind of parameters in a separate table with only 1 row. You can put things like this in it, but also the name of the application, company name (which could change sometimes), data of last backup and so on. It makes your application more flexible. Hope this helps. Tony From: [email protected] [mailto:[email protected]] On Behalf Of tfred Sent: woensdag 30 januari 2013 12:30 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
