At a couple of sites recently, a compiled EXE has produced an error (1104) when trying to read FoxUser.dbf when closing down. When I checked, this file did exist in the directory it mentionned - but it's nothing to do with this application. The specified directory containing the file is on the computer's path statement, however.

I'd like to understand more about when an EXE (as opposed to VFP itself) tries to read this file, and where it tries to look for it. Can anyone enlighten me please

If you're not using it on purpose delete it. It'd be created automatically. Putting:

resource=off

in config.fpw turns foxuser.* usage off. Generally it's not needed and VFP seraches for it in exe working folder unless specified otherwise.

Thanks for that. What I'm talking about, though, is a distributed application. The FoxUser file it's trying to read on closedown is not one of mine. I can't be sure whether other applications may create FoxUser.* somewhere. If the directory containing this happens to be in the computer's path statement then it seems that my application will try and read it - and complain if it can't.

If I SET RESOURCE OFF in my app, will that be enough to prevent it trying to read FoxUser.* when it closes, even it finds one laying around somewhere

Correct.

As Cetin said, put resource=off in your config.fpw file