>When I do a search on the archive files for Config.fpw naturally I get pages and pages of threads just for year 2005.
>
>Does anyone have any thoughts on what should be in a config.fpw file for the following:
>
>1 Just a standard development machine withe evrything on the local machine and using an SQL 2000 database (on another machine).
>
>2. A client application (my VFP EXE) with the application on a network drive and the database SQL 2000 on a dedicate SQL server.
>
>
>I know this is sort of like asking "What kind of car do you like". Everyone has different thoughts. I already have a config.fpw but I would appreciate any thoughts and suggestions that might optimize my application..
>
>Joel
>Houston, TX

I keep as few lines as possible in config.fpw, everything else is in my loader program. My loader program reads and sets all my preferred settings from a table, checks for updates and then start my application or the IDE. In config.fpw, I only have lines for resource, overlay, editwork, sortwork, progwork and tmpfiles. I am sure that some of these lines are redundant in VFP, but I have used the same config.fpw files for the last 10-15 years, so why change them?

In a config.fpw file to include in an application, you also must include screen=off.