Normally a SET PATH TO would be sufficient. If you're using a DBC, then just explicitly open that DBC with the provided path is all you need.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Gene Wirchenko Gesendet: Mittwoch, 14. August 2019 05:58 An: ProFox Email List profox@leafe.com Betreff: SET DEFAULT or ?
Hello:
I have an app that has for years been executed out of the default directory with the data there, too.
Now, I have to give at least the data an arbitrary location. Can I use SET DEFAULT for this and save having to rewrite hundreds of table referring statements? Or are there nasty things to worry about?
I am thinking of having a config table in the startup default directory that specifies the data directory and then SET DEFAULT to that directory. When executing a .exe version of the app, I think this will not cause trouble, but for a debug version with separate .fxp, I think I also need to SET PATH for the code to be found. I join all my code together with SET PROCEDURE TO ... ADDITIVE in the startup .fxp if that makes a difference. Are the gotchas going to get me?
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]