>I don't rely on CONFIG.FPW to set up data paths; instead, I use it to establish the runtime environment (things like TMPFILES, the status of the main VFP window before the app gains control, etc), and use a shortcut with the -c command line switch to point to a station-specific CONFIG file. I also embed a default CONFIG.FPW in the app - that way, I can establish some reasonable defaults that take effect in the event that the station-specific CONFIG isn't available.
>
>The application code can gain control and set up data paths and the like before opening files, so a resource like an INI file or the Windows Registry can be used to point at data. You can also pass parameters on the command line to the main routine that point to a data path, or an INI file, or whatever, to establish the application context; it doesn't have to be established before the application code gains control.


I didn't have any luck with that -c switch. It still ignored the config.fpw. INIs and the registry are beyond my ability, and probably over-kill just to have one line to say "hey, the data's in this directory".

I did something so that it finds the data all right now when I run from VFP. I'm drawing a complete blank on what I did right now, though.

The problem I'm having now is that the "cancel" at the end of the app cancels VFP and leaves the app! How do I tell it to end the app and leave VFP running?

Thanks,