>I've got a client who is using a package written by my company in VFP 5.0. Our package is installed on 5 different laptops there (all of the laptops are Toshibas), and the software works on 4 of them. The 5th machine gives the error "VFP500.DLL is invalid or damaged" when they try to start the software. We have replaced the VFP500.DLL with a copy from one of the working machines, but are still encountering the error. We have checked the file size of the DLL, and it matches the other VFP500 files (3,223,824 bytes). We have also had the client reinstall our software from scratch. As far as we can tell, the DLL is fine, but we are still running into the error. The other VFP DLL's appear to be okay as well (VFP5ENU.DLL, VFPOLE50.DLL, and VFPODBC.DLL). Can anyone think of any reason why VFP would be balking at what appears to be a valid DLL file? Any suggestions for resolving this situation would be greatly appreciated.
>
>----
>Eric Rolfe
>Building Technology Associates

Eric,
This is just a shot in the dark, is there another VFP500.dll on the system that your app finds before it gets to the one that matches the others?

(shrug???)