My CAD 0.02

I have found that VFP seems, irrespective of the CONFIG.FPW setting to want to use any FOXUSER.DBF it may find in it's search path if it cannot find the specified one, or if RESOURCE is set OFF in the config file.
This has happened to me a lot where the servers had stray FOXUSER files left over from other legacy apps, and the user had search/read rights only (Novell Servers).


>>Apologies Barbera ....
>>
>>I've been teethed in VFP 6+ environment, and am a bit of a 2.6 newbie, so I didn't realise that the Config.FPW was actually built into the executable as part of the project in this instance. Whether this is good practice or not is another question. It is this which was causing the difference between old and new Exe's, as the tmpfiles path specified was pointing to a read only location on the local PC. Thanks for the help ...
>>
>
>FWIW, this would apply in VFP as well, although you generally don't need to direct temporary files to the local workstation like you did in 2.X. It's still a common practice to include the config.fpw in the EXE though.