Actually, those two files are the run-time. The problem is that you may also need the right version of several Windows DLLs. Some of your machines may have older versions than VFP requires. The best way to make sure you have recent enough versions is to create installation disks and install them on each workstation. This way you'll update any old DLLs but not overwrite any newer ones.

>Josh -
>
>Thanks for the advice; I didn't go through the setup wizard, but I didn't think the runtime was needed if you create an .exe file. The build.exe command just indicates that two support files (those .dlls) are needed in the same directory or along the DOS path. Do I have incomplete information, or is it your experience that including the runtime even when you have an .exe?
>
>Sylvia
>
>>Sylvia,
>>
>>It doesn't sound like a memory problem. I think it's more likely to have to do with what's installed on each computer. I would advise creating setup disks with the setup wizard and installing the run-time on each. There may be a Windows dll that is out of date or something like that.
>>
>>>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