I am having a similar problem running an application off a novell network. In most cases you can get away with keeping both the executable and the .dll files in a network directory and then launching them to run to a local machine without doing a local install. And the application runs fine on newer machines, but on several of the older ones (P75), the user gets the same message you saw (.dll invalid or corrupted)(This is, by the way, Fox5). It's apparently related to the windows registry, in that on most machines, running the application registers FoxPro applications with Windows, but not on these particular machines. The question is: Why?, and specifically, what else is going on, and how can I fix it? If you or anyone reading this message finds out, please let me know.

>I believe other people have had similar posts,
>the thing is these files must be installed and
>cannot be copied.
>
>You might check microsoft's site for updated setup
>wizard. Hope this helps. Have a good day.
>
>Becky
>
>
>>Recently we installed Service Pack3. No problems.
>>However since then, whenever we install our application on client's PCs, about 1 in 3 will produce an error when invoking the application.
>>
>> VFP500.DLL is missing or corrupted
>>
>>OK, we then look for vfp500.dll and it is there. Just in case it got corrupted, I copy the vfp500.dll from a system where our application is running fine onto the system where Win95 complains about the DLL. After this copy I still get the same error message. Clearly something else is missing, but what??
>>
>>The PCs were our application runs fine have a recent version of Win95. The ones that have problem seem to have the original Win95, with subsequent install of updates. (Although this is often difficult to confirm as our clients don't know for sure)
>>
>>Prior to us installing VFP service pack3 we did not appear to have this problem.
>>
>>Here is a list of the Win System files that are installed with our app:-
>>
>>comcat.dll Foxpro.int Hlp95en.dll mfc40.dll mfc41.dll
>>msvcrt20.dll msvcrt21.dll oleaut32.dll olepro32.dll stdole.tlb
>>vfp500.dll vfp5enu.dll vfp5ole.dll
>>
>>I suspect our installation is either missing a Windows System file or not detecting and updating an old Windows System file on the client's computer. Any ideas/suggestion as to what is happening?
>>
>>regards,
>>
>>Alain