>>You can also compile a config.fpw into the application when you build it.
>
>
>Hi David.
>
>
>It's only a kind of configuration file, and is completely unecessary !
>
>
>CLAUDIO

Hi Claudio,

I have to disagree. The Config.fpw can be very important.

First, you use it to configure the environment of the applications you distribute. You can control where the temp files are written, whether the VFP Desktop appears on opening, optimize memory use, set titles of opening windows, etc.

Second - and this is critical - FoxPro will look for a Config.fpw file when it or an application written in Fox is run. If you don't specify one, VFP will use the first one it finds. I learned this the hard way years ago when I didn't compile in a config.fp into a FoxPro for DOS app that was distributed to about 100 offices. Many of them ran eratically or not at all because FoxPro found a Config.fp in the root of C: from some other FoxPro developer that set defaults to drives that were not mapped for the currently logged in user.
Needless to say those people were not happy and I have included a config.fp or fpw in my applications ever since.