You can call application using configuration file having:

path=...
default=...

individual for local PC (run YourProgName.exe -Cconfig.loc).




*---------------Your Message below

On my development machine I typically have a data directory set on the path for each project. I also have several sets of data (user data) in other directories, either local or on the network. It has always bugged me that I could not access these sets of data, running the main form from the command line, or running the .exe for the app - it always accessed the data in the original test data directory.
Yes, I know that's due to the path being stored, and never a problem on a production machine because we set a path, and the stored path directory does not exist.
One school of thought suggested that problem was the path stored in the .DBC, but this turns out not to be so. Short answer has been to rename the the test directory whenever I want to work on another set of data. That is, until while in a user directory, I made a change to a form, which called a pick list, and the pick list failed to work.
Turns out that saving the change stored the new path for the database in the calling form. Easily resolved.
I know there are arguments for and against storing paths, but is there a way to turn it off? It may be 'by design', but it creates a minefield.
Previous - Next - Reply