>I have had an issue recently that surfaces because at run-time, VFP uses the Windows temp directory (unless TMPFILES et al are in the config.fpw file).
>If the temp directory is a System folder, VFP won't (can't?) read (or write?) to it.
>When I set up the Windows temp directory, it is not a System folder. It is not a System folder for weeks. And then one day it is. I reboot everyday.
>
>What gives?
>Why isn't it a System folder from the get-go?
>Why does it suddenly become one?
>
>FWIW: We're trying to avoid using a config.fpw file, since we may have hundreds of COM projects and we would like to avoid having to either (1) remember to include the right config.fpw file or (2) create a project creation tool (although this one isn't so bad).

Trey,

Whether or not the temp directory is a system folder is determined by the folder's attributes. Something may have set this attribute. Why? I can't say. Anything, however, (file or folder) that's marked as system is exclusively for the use of the operating system. While I haven't checked further, I would assume that this would mean that VFP can't write its tmp files there.