Hi Jeff,

Thanks for the reply. Sounds wierd, but I'll check it out

Rgds

>Also check the swap file size on those work statations. I ran into this once and had to increase the size of the swap file and all was well.
>
>
>Jeff
>>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