>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


Sylvia,

I found this same problem - look up MS Knowledge Base Article Q158064, it may help you. Cause was a outdated oleaut32.dll. Be careful with NT, I found a article about not copying this file to NT but I don't recall the article I found that in (VFP5). (In VFP6.0 the documentation says its okay to copy the newer one.)

Robert