Thanks Tamar.

That definately looks like a possible cause of the problem, I will look into it.

Chris.


>>
>>Chris.
>
>Here's what we said about all this in HackFox. Bottom line is if you don't specify the location of a config file, VFP is going to look down the DOS path (which I'll bet includes the system directory).
>
>---
>Config.FPW stores a number of SET commands, as well as some special options available only in this file. How Visual FoxPro determines which Config.FPW file to use is a bit tricky. In the development environment, Visual FoxPro first checks to see if Visual FoxPro has been started up with the command line –C startup switch. If you've modified the shortcut's properties, or created a command line, such as:
>
>D:\VFP\VFP.EXE -CD:\PROJECTS\CONFIG.VFP
>Visual FoxPro uses the specified file. Next, Visual FoxPro checks for a DOS environment variable FOXPROWCFG. If this exists, the file it points to is used. If not, Visual FoxPro searches the current directory, and then the DOS path for a file named Config.FPW. VFP uses the DOS path only, because the FoxPro path has not yet been established.
>
>The runtime environment operates a little differently. For an APP or an EXE, besides using the methods above, you may include a file named Config.FPW in the project, using the Other-Text Files section. Visual FoxPro uses this file before starting the same sequence as the development environment.
>
>Tamar