In addition to Barbara's suggestions, if you include an CONFIG.FPW file in your project and then compile it into your EXE, it will always be used. You can't override it.

>I have a Config.FPW file that looks like:
>
>keycomp = windows
>sortwork = C:\TEMP
>progwork = C:\TEMP
>editwork = C:\TEMP
>mvcount = 1024
>path = data;reports;bmps;html;worddocs
>status bar = off
>status = off
>resource = off
>clock = status
>exclusive = off
>deleted = on
>multilocks = on
>command = _Screen.WindowState = 2
>
>I received an errorlog from a user that collects details about an error when an option hurls. Here are 4 lines from the errorlog regarding an error:
>
>Current directory: V:\
>FoxPro start dir: C:\WINDOWS\SYSTEM\
>Resource file: V:\FOXUSER.DBF
>Temporary file drive: C:\WINDOWS\TEMP
>
>
>1) Why is the "Temp file drive" C:\WINDOWS\TEMP instead of C:\TEMP as specified in the Config.FPW file?
>
>2) Why is the start dir C:\WINDOWS\SYSTEM? Is this determined by the location of the VFP runtimes? If so, should i have a copy of CONFIG.FPW in the WINDOWS\SYSTEM folder?
>
>3) I do not specify and do NOT want to specify a config file name as part of the call to launch the EXE (i.e. C:\Vfp98\VFP6.EXE -CC:\MYAPP\MYAPP.FPW). I thought by naming the config file CONFIG.FPW, VFP would find it. (The file resides in the same directory as the EXE that they run.) Is this the case?
>
>thanks...