>I got this message from a user:

>The VFP EXE won’t open for me.
>Is there a problem with the system/program?
>What can I do to fix it?

>I took a look at the computer she was using, which is a Win2003 Server dedicated terminal server machine used by several users via Remote Desktop Connection (and this is how she was using it). So I tried to run the VFP EXE as usual. Would not run. Reported "invalid vfp8r.dll" . Here's what's odd: The _valid_ vfp8r.dll was still where it was supposed to be in "C:\Program Files\Common Files\Microsoft Shared\VFP". However, within the VFP EXE's home folder was a corrupt DLL file also named vfp8r.dll, about half the size of the actual DLL. Its creation date was about 3 days ago. Since the windows loader always first looks in startup dir of an EXE to find support DLL's, it errored out on startup. I have _no_idea_ how that DLL got there. I renamed it to vfp8rbad.dll and the EXE then found its correct DLL in the Microsoft Shared area and now runs fine again.
>
>Has anybody else had this kind of thing happen? It seems at first glance that somebody intentionally tried to hack the app.

If it's not a virus, it may be sabotage. What's in that dll?