Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Config.fpw conflict between 2 apps

Status
Not open for further replies.

mkrausnick

Programmer
Apr 2, 2002
766
US
I have a VFP utility (a .EXE) that runs with no user interface, so I have a 1-LINE config.fpw in the project that contains SCREEN=OFF. It usually runs fine.

Recently I had occasion to run it while the home folder of another VFP application was the current folder. That application has its own config.fpw.

When I ran the utility, I got a dialog box with the message "Resource file version mismatch". Clicking OK yielded another dialog box with the message "Visual Foxpro could not start. Resources could not be loaded". If I delete the second application's config.fpw, the first utility runs OK from the same folder.

I'm not running the second application at the time; it just so happens that the second application's home folder is current when the utility runs.

How can I get the utility to run without an error even if the current folder contains a config.fpw?

Mike Krausnick
Dublin, California
 
you compile the config.fpw into your exe, don't exclude it from compilation, then the exe should ignore any other config.fpw file present as long as you don't run it with the command line switch to provide another config.fpw

Bye, Olaf.
 
You might like to add ALLOWEXTERNAL=OFF to the Config file that you include in the Exe to make sure that Fox doesn't go looking for any other config files. This is the default setting but it does no harm to state it explicitly.

Geoff Franklin
 
Tried the ALLOWEXTERNAL=OFF fix, still got the error. I discovered copies of the VFP DLL libraries in the same directory, so I deleted them and the problem went away. The oddity is that they were VFP9 libraries, and both apps (the utility and the app in the folder where the error occured) were built using the same version of VFP.

Anyway, thank you both for your time.

Mike Krausnick
Dublin, California
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top