You might also want to check to make sure the is no FOXPROCFG environment variable set. I *think* that's the name I seem to remember. I'm not even sure that VFP uses it, or if it does use it, if it overides a -C setting from the start up. FWIW.
>Hi Fred,
>
>The CONFIG.FPW file resides on the Network in the same location as the Exe.
>I have even recently tried calling the exe with the -c option to get rid of any ambiguity by specifically pointing to the right config file.
>Works on most PCs, but the odd ones are still driving me nuts!
>
>>Sure it does. Each workstation uses it's own CONFIG.FPW, so they each could be referencing different TMPFILES or not even have one at all, so it's using the Windows default! Another thing you might check is that the C:\MYAPP\TEMP folder even exists on each workstation and that it's not hidden or psome other user rights issue in accessing it.
>>
>>
>>>Thanks, I'll try that.
>>>... Still doesn't explain why only some workstations report experience the error. All the other things being equal, it seems to point to user and/or workstation login script/setup differences.
>>>
>>>>Can you put some code in your app to make sure you're using the CONFIG.FPW file that you think you are? Add a WAIT WINDOW SYS(2019)to your app and see what it says.
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>I'm running into a problem with my app that has recently surfaced, and is inconsistent:
>>>>>
>>>>>I have a small startup EXE which resides on a Novell Server, in a directory that the user has read-only rights to.
>>>>>The built in CONFIG.FPW sets TMPFILES=C:\MYAPP\TEMP.
>>>>>I also have a copy of the CONFIG.FPW on the same drive/path as the exe.
>>>>>The users are running Win 95 (!), WinNT, and Win 2000.
>>>>>This works well for most PCs.
>>>>>However, some PCs running the app get the responses/errors
>>>>>"Update resource file Yes/No"
>>>>>"Unable to create program workspace"
>>>>>
>>>>>... which seems to indicate that VFP is attempting to create its temporary workspace files on a drive/path to which the user has no create rights.
>>>>>
>>>>>This seems to be confirmed by the fact that, if I login, the error does not appear (I have near supervisory rights).
>>>>>
>>>>>Any explanations/suggestions? This problem occurs on only on a few workstations.
>>>>>
>>>>>TIA
