>OK, here's a good one,
>
>We've developed a VFP5 application for my company. Out of roughly 150 installs, 9 computers display the error:
>
>VFP500.DLL invalid or corrupted
>
>There seems to be no rhyme or reason to this problem. These few computers simply do not like the VFP run-time file, period.
>
>We've created a shared file, distributed multiple files, gave users full access, restricted users access, deployed on NT, deployed on Novell, made the DLL read-only, made the DLL read-write, upgraded the PCs - added more RAM. None of these changes made any difference at all.
>
>In the end (about 2 months and 4 technicians) :
>
>- 7 computers were upgraded from Windows 95 A to Windows 95 B - this was a little tricky but solved the problem.
>- the other 2 computers' motherboards were discarded and replaced.
>
>Can anyone shed any light on this topic? Are there patches for VFP5? This is a real pain in the neck!
>
>Thanks,
>John Morga

Check Microsoft's knowledge base article Q158064 "VFP500.dll is Invalid or Damaged".