>>>I'm trying to avoid creating a special local directory on everyone's machine to house varying CONFIG.FPW files. I want the user to be able to run the .EXE from the network where I will mantain ONE CONFIG.FPW file. Then it would be nice if my app could determine a local directory to use (IE: \WINDOWS\TEMP, etc). The only problem is: Can the CONFIG.FPW variables, EDITWORK, PROGWORK, SORTWORK, TMPFILES be set dynamically during runtime?
>>>
>>>Or do we HAVE TO make local directories for every machine and the matching shortcut to point them out?
>>>
>>>My way would be so much cleaner...(but can I do it?)
>>>
>>>Thanx all!
>>>
>>>Joe
>>
>>You can't set the ...WORK directories after FoxPro has started up. But, by default, these settings should default to the local Windows temporary directory anyway.
>
>No, by default, they go to the starting direcotry for the executable. Read the documentation for Installing and Configuring VFP - it spells this out in detail.

Thanks for pointing that out Ed. This explains a problem that I am currently experiencing, but I had ruled out temporary files as the reason due to this misunderstanding.