>Terminal Server 2003. (Sorry about the wrong version information in the header, this is VFP8 SP1 not VFP9) workstations are Windows XP.
>
>On terminal services c:\ is the terminal server local hard drive, not the remote hard drive. I have directories setup for each terminal services user as such:
>
>c:\users\user1
>c:\users\user2
>
>The environment variable of username stores the terminal services client username for me so I can put the following in the client's desktop shortcut and it runs the correct config.fpw:
>
>c:\profiler\pro32.exe -cc:\users\%username%\config.fpw
>
>this runs config.fpw in the correct users directory as it should, however, I cannot get the environment variable to work inside of the config.fpw. I need to do the below:
>
>EDITWORK=c:\users\%username%\tmp\
>PROGWORK=c:\users\%username%\tmp\
>SORTWORK=c:\users\%username%\tmp\
>RESOURCE=c:\users\%username%\vfpuser.dbf
>TMPFILES=c:\users\%username%\tmp\
>
>But it only takes if I explicitly put in the folder as in:
>
>RESOURCE = c:\users\user1\vfpuser.dbf
>
>I am overlooking something obvious, can anyone see it? The environment variable of username in this example is 'user1' and the desktop shortcut works but the username system variable is not swapping to user1 in the config.fpw file itself.
>
>TIA

Hi Tracy,

I am not familiar with Terminal Server but from what you described, it seems, unlike CMD.EXE, VFP does not honor the environmental vars substitution when it parses the config.fpw.

Rather than calling your VFP app directly, is it doable in your case to create a desktop shortcut that calls a CMD batch file (which honors env var substitution) which does two things:

(1) dynamically generate a config.fpw file in the right location
(2) calls your VFP app in the normal way