FoxPro or Windows XP Problem

[Menglish]

When I create an EXE file from VFP 6.0 or 7.0 and attemp to run it using a shortcut from the desktop, I get the FoxPro error message "Error locating the config file--bad path?" and this is before the PRG loads. After this, the program runs fine.

My question is; Is this a Windows problem or a FoxPro problem? I tried re-installing FoxPro but had the same error result.

Anyone else ever experience this?

Thanks for any ideas,

Millard

 

[AirCon]

I'm not sure about this. Do you use/include config.fpw ? If you use it, can you post what is your config.fpw looks like ?
If you run the app under VFP IDE, does it throw the error message ?



-- AirCon --

 

[Menglish]

Hello AirCon,

I do not include my config.fpw when compiled. I have a command line to "set path to curdir()" and put everything in one folder.

When I create an app and run it, I get the same error message.

This program has been running fine for about 6 months and suddenly, two days ago, I got this error message.

I checked and do not have a virus, defrag did not help, Norton Win Doctor found nothing wrong.

Because this occurred suddenly, and the problems exists in VFP 6 and VFP 7, I tend to suspect the Windows XP system but wanted to check first to see if anyone else had experienced this.

Millard

 

[rgbean]

Millard,
Unless you specify where the config.fpw file is in your shortcut - e.g. C:\mydir\myapp.exe -cC:\mydir\config.fpw
then VFP expects to find one in the current directory.

What OS is this failing under? Does your user have the proper rights to access all the directories in the CONFIG.FPW?

Rick

 

[Menglish]

Hi Rick,

I am operating Windows XP Pro with Administrative privileges. This program has been operating fine and still does after it halts and displays the message.

I just downloaded a file from Foxite (an EXE) and got the same message. I am trying to determine if I need to do a full uninstall then re-install of VFP 7.0 or Windows XP Pro or if something else is the culprit.

Kindest regards,

Millard

 

[DSummZZZ]

Just a thought.
One thing I've noticed about XP is that it draws the desktop icons prior to establishing network drive mappings. If you have a network drive mapped as say, "G:" which points to a directory on a file server, the G: drive mapping can get replaced with the UNC i.e., \\Servername\Volume\Subdir.....etc., at start-up. So if the app is started before the mappings get established, which usually doesn't happen until they are accessed via explorer, the app may not see your config if it is on a server. I fixed this by making the shortcut read only on my XP boxes.


Dave S.

 

[AirCon]

Hi Millard,

Another suggestion.

Go to DOS-Prompt, change the directory to VFP7 directory. Then type in: VFP7 /regserver

Open VFP7, go to home() directory, and run VFPClean.app


-- AirCon --

 

[mdav2]

I have had one instance of this on a windows 2000 machine running a vfp6 database. We have run the same app without this problem for 2 years and on the same operating system. We don't use a config file in the path. When we solve this I'll post our solution.

 

[craigsboyd]

Make sure that the shortcut has the right Start In path in it. Also, delete all config.fpw files except for one on the machine and also try deleting every instance of the resource files (Foxuser.*) on the machine. You could reinstall VFP if none of this works, but if this is happening on a user's/test machine after the install of your app then that is probably not it. Check to make sure you are using the latest service pack on the VFP product when you compile your app and create your install. Also you could check the system files for the OS by issuing "sfc.exe /scannnow" from the Windows RUN command (not in VFP)...this will check all your system DLLs. If that all fails then try to build a very small and simple EXE and try to see if the problem persists. Get rid of the Config.fpw completely and see if it is still errors out. And if all that fails and you have exhausted all your time and energy as an absolute last step after you have called MS and given up all hope of getting a solution here, you can reformat your drive and reinstall windows then reinstall VFP. That's a brief guide to playing Battleship with VFP to figure out what is wrong and fix it by trial and error when you haven't a clue why the error is occuring.

Slighthaze = NULL
_{craig1442@mchsi.com}

"Whom computers would destroy, they must first drive mad." - Anon​