>>Using VFP 5.0 and only one of several users in an office is getting a foxpro "Error locating config file - Bad Path?" whenever they try to run the application EXE. No one else in the office has a problem. All are running Windows95 with the Microsoft network. The exe is on the server. This error message does not seem to be listed in Foxpro Help. The config.fpw has been compiled into the exe and references C:\TEMP for its work locations. Have verified that the workstation has this directory and there are no attribute flags (hidden, system, etc.) associated with it.
>>
>>Does anyone have any ideas or things we might try to correct this?
>For "work locations" you mean progwork, sortwork etc ? They are determined when exe is loading. It's better if you keep config.fpw as a plain text file within the same dir of exe.
>Cetin

The problem was with the DOS PATH environment setting!

That particular work station had a missing semicolon (;) in the SET PATH= statement in the AUTOEXEC.BAT file, and that was generating this error when the VFP 5.0a application was starting. I'm not sure if it would have mattered if the CONFIG.FPW were not compiled into the EXE, but I really did not expect the DOS path to affect VFP finding the CONFIG.FPW in the same directory as the application!

(I work in the same office as Ken Luther)

-Lou Harris.