I put these dlls in the same directory as my application on the Server:
VFP500.dll, VFP5ENU.dll, VFPODBC.dll, VFPOLE50.dll.

Also, be careful when passing parameters to an EXE. If your parameter starts with a "/d" - this will also cause that error.

Hope this helps.


>We are currently running a number of pc's in a training environment where we have configured windows 95 to run off the server. For the most part, everything is running fine. However, we have a VFP 5.0a application that we wish to run from the individual stations, but when we do the netsetup it copies the vfp500.dll and associated files to the server's system directory and when the application is launched, a "Bad or Invalid VFP500.DLL" message is received. We have tried updating the OLEAUT32.DLL on both the server and local pc, have copied the VFP*.* files to the local windows\system directory, all to no avail. Does anyone have an idea I can try? Thanks -- Charles