Re: which operating systems support MFC71*.dlls ?

No, it is deeper. For example, MFC version x.y uncovers a bug in OLEAUT32.DLL or
something like that. It is fixed in release version x.y+1 by including a new
redistributable DLL with the installation. So if somebody uses it on a version of WIndows
that only has the old version of the redistributable DLL (e.g., p.q, where the new version
might be p+1.1) then it won't work on the older machine. We've had it happen. Since some
of our products use third-party DLLs that use COM, we've been nuked by it.
joe

On Mon, 23 Apr 2007 04:39:28 GMT, "David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote:

"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:om4o23pfs40gsqn62aiacuhmpll89rcauu@xxxxxxxxxx
Most of the problems we've had with people copying the .exe file to
another machine deal
with obsolete DLLs in other areas, such as COM/OLE support. If we built
on XP and they
move to Win2K, there have been problems.

If you mean you set the _WINVER and _WIN32_IE defines to be XP, then yes,
you might very well have problems if you deploy on 2K. But this affects
dynamic linking as well as static linking.

-- David

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.