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
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/000a01d15212$d3ccd340$7b6679c0$@powerchurch.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
