I don't know about InstallShield, but we do it with the Wise installation system without a problem. The one thing to remember is to NEVER replace the file on a NT 3.51 machine. We brought several NT 3.51 machines to their knees doing this. Supposedly if an NT 3.51 machine has Service Pack 5 applied, the file is OK but we haven't tested this.
>Thank you very much.
>
>Do you know if Installshield 3.0 will take care of replacing the DLL under various operating systems as VFP setup wizard does. ?
>
>
>>>I rebuilded in VFP 5 the EXE of a very simple application I developped in VFP 3, and moved it to a different PC in a directory together with VFP500.DLL (instead of the old VFP300.ESL).
>>>
>>>The problem I got is that when I double click in the EXE to run the application, I get the message "The VFP500.DLL file is invalid or damaged".
>>>
>>>If I execute it in the same PC where I have VFP5 installed, then it works fine.
>>>
>>>Which other files do I need to run the EXE ?
>>>
>>>Any help will be very appreciate
>>>
>>>P.D. I can't use the standard foxpro setup because I need to use installshield.
>>
>>This is the result of an out of date OLEAUT32.DLL file on the PC you moved the .EXE to.
>>
>>Check out the KB article at
www.microsoft.com/kb/articles/q158/0/64.htm for info on how to replace this file under various operating systems.
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
