I guess you know that you can specify the config.fpw file, by the -C switch? And the configuration file doesn't have to be called config.fpw, you can call it whatever you want. "C:\Omnia\OIS4\Rick\MyProg.exe -cRick.26" will run C:\Omnia\OIS4\Rick\MyProg.exe which will use the file Rick.26 asin stead of config.fpw.

>Tore,
>I forgot to mention that I didn't want to use config.fpw: TMPFILES
>If I have to I will but I'd prefer to not use it. I have 2 programs that use config.fpw, and the content of the config.fpw is different. I'm not sure if I can merge them into one config.fpw. I need to start both programs from the same starting place, and I need them to point to the same temp directory.
>One program is VFP 5, and the other is FPW 2.6
>I'm not sure what would happen if I merge the config.fpw files.
>
>What I have is a directory structure like
>C:\Omnia\OIS4\UserName\Temp
>When a user logins in UserName is set to their login name. Let's assume the user is Rick... When Rick logins in he has a short cut that points to a FPW 2.6 executable (MyProg.exe)in C:\Omnia\OIS4\%UserName%
>That shortcut executes C:\Omnia\OIS4\Rick\MyProg.exe and uses the config.fpw found in Rick. The config.fpw has TMPFILES=C:\Omnia\OIS4\Rick\Temp
>
>I could use the same approach, if I could merge the two config.fpw, but it doesn't look like I can.
>
>Any ideas?
>Rick
>
>
>>>Is there anyway to programatically set the value that sys(2023) returns?
>>>I suspect there is. I suspect there is because you can go to Tools\options and under the Files tab you get to specify the value that sys(2023) returns.
>>>
>>>I'm hoping that means I can do it in code.
>>>
>>>TIA,
>>>Rick Liebespach
>>
>>You can set this in Config.fpw : TMPFILES=yourTempPath