>>I built an exe that loads and runs fine on 4 computers, but on two other computers get a message similar to "Vfp500.dll invalid or corrupt" and the program goes no further. The .dll is in the same directory as the .exe file. The two machines which have this problem have 32Mg of memory. Coincidentally (or not), I also can't register the comdlg32.ocx on either of these two machines. Has anyone seen anything like this before and/or does it sound like a memory related problem (the other machines have 40Mg or more)?
>>
>>Thanks for any ideas!
>>
>>Sylvia
>
>The VFP500.DLL belongs in the Windows\System32 directory.

Craig -

I had tried that on one of the computers that had the problem, but got the same message (although they didn't have a System32 directory, rather a System directory; does a System32 directory indicate there may be different kinds of .dlls associated with different version of Windows 95 or are we just talking about a different name here?). Anyway, I was following instructions from the Build.exe help which says "...Build.exe requests two support files: VFP500.DLL AND VFP5ENU.DLL...These files must be placed in the same directory as the executable file or along the MS-DOS path."

Sylvia