>If you need to customize the application based on the user/workstation, you might be better off using an .INI file or storing the appropriate settings in the registry.

The problem is customizing VFP to the workstation's environment; we don't put stuff that can be fixed after VFP starts in the CONFIG.FPW, just things that have to be established before the application starts, like the temp files issue, SCREEN = OFF and RESOURCE = OFF. Anything that can be fixed up after VFP has started doesn't belong in CONFIG.FPW from my POV, but clearly, my position doesn't represent everyone else's standard approach to the problem.

Whatever works for you is fine by me; this strategy serves me well.