>Hi!
>
> Why not include MSVCIRT.DLL into your setup program, so you will be sure both DLL are instaled and in synch?
>
>>We've run into a bit of a problem with distributing an app. We include the MSVCRT.DLL to be updated, but this causes a problem with another .DLL that VFP doesn't use. The .DLL in question is MSVCIRT.DLL and seems to go in synch with MSVCRT.DLL, at least both versions on my box have the same version number.
>>
>>Our problem is that when we distribute a newer version of the MSVCRT.DLL, it gets out of sych with MSVCIRT.DLL that may possibly be already on the box and then the software that requires MSVCIRT.DLL no longer runs.
>>
>>Any suggestions?

If that's what we have to do, then so be it. But our problem is, How were we supposed to know this? MSVCIRT.DLL is not listed as one of the files we need to distribute, nor is it in any of the dependencies of any of the other files we distribute. It just has as one of it's dependants MSVCRT.DLL.

How are we supposed to tell if there are any others with this same or similar situation?

Greetings from DLL Hell! Wish you were here! < g >