Hello everyone,
I've tracked this down a little further. Using the SysInternals Process Monitor program, VFP is looking for the FOXUSER.DBF. In the process, it looks in the current folder, then every folder in the PATH. There bad path does not appear in the captured data.
Having a valid FOXUSER.DBF in the program folder prevents the error from happening.
This still occurs even though the compiled in config.fpw file contains the line: resource=off
I am now testing with 09.00.0000.7423
This wasn't a problem with an exe built using 09.00.0000.3504, until I modified the exes internal manifest.
Any thoughts?
Tracy Pearson PowerChurch Software