Craig, about:
> If the user doesn't have permission to write to the temp folder, VFP will not even launch
I did a short test renaming my c:\Temp directory to c:\temp_ and my exe it still works.

Dmitry, if you have frequent crashes the Temp folder results full of undeleted *.TMP files.
It may still happen that Fox generate a temp name i.e."000084QX000A.TMP", the same as a previous undeleted temp file, so errors still occur.
I also suggest to delete all old TMP files in the temporary directory.
Just my guess.

Thank you.
Bruno



>Nice theory, but not quite true If the user doesn't have permission to write to the temp folder, VFP will not even launch. The best solution regarding temp folders is to not specify one at all. Then, VFP will use the temp folder specified in Windows settings.
>
>>>Maybe the issue is permission-related.
>>>When the file "V_WO_NUM" is physically written to disk (as "V_WO_NUM.tmp", no, as i.e."000084QX000A.TMP"), since it becomes too big to be kept just in memory, you got the error since the user doesn't have permission to write in the Temp folder you selected in your config.fpw file.
>>>If you have a config.fpw with code like this:
>>>TMPFILES=c:\temp
>>>EDITWORK=c:\temp
>>>PROGWORK=c:\temp
>>>SORTWORK=c:\temp
>>>
>>>be shure that the user has full permission on c:\temp; or just delete those statements, so files are created in Windows Temp directory.
>>>
>>>You never get the error since you likely are administrator on your local computer, so you can write in the given folder.
>>>
>>>HTH
>>>Bruno
>>
>>Very interesting theory. I wonder how I can 'simulate' this on my computer. Thank you!