>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?
>

No, they can only be set before the runtime environment is established. See the VFP on-line help; it spells this out in detail.

>Or do we HAVE TO make local directories for every machine and the matching shortcut to point them out?
>

That's another option. A third option would be to put a copy of the .EXE locally on each station in a directory, and run from that directory. By default, VFP will put its temp files in the starting directory.

Another option would be to build a CONFIG.FPW for each machine and put it somewhere on the system, and use the FOXPROWCFG environment variable to point to the local station's CONFIG file. You'd set the environment variable in AUTOEXEC.BAT under Win9x, and NT provides a mechanism to set default environment strings as well.

>My way would be so much cleaner...(but can I do it?)
>
>Thanx all!
>
>Joe