>We have a couple of procedures left over from FoxPro 2.6 that still work for us, but now that we have released it to clients we are getting sporadic errors. The error is error writing to foxuser.fpt. We didn't have this issue in VFP 6 just now that we have upgraded to VFP 8 SP1. It's always on a READ statement and in our error logging program we logged that RESOURCE is set to OFF but it is set to c:\windows\system32\foxuser.dbf, which is the default when you have RESOURCE=OFF in the config.fpw. The users don't have access to their system32 folder because the IT guy doesn't want them to, but it shouldn't matter since RESOURCE is OFF. Anyone seen this or know of a work around currently we catch it in our error logging program and just ignore it. I have a hunch it's when they sit on a read statement for awhile but don't know for sure since I can't recreate it back here.

You can circumvent this by having a separate resource file for each user, so even if some stray routine tries to do something with the resource file, it won't be the one in the system directory, but rather something in a local directory. You can just copy the original resource file (or "copy next 0" if you want structure only) to user's private resource file, keep Set Resource Off and see what happens. After a while you should be able to find out what's trying to write into it.