> I have written a program that is dynamically linked to the mfc
> libraries. Some of our users have complained that it is giving the
> error "Linked to missing export MFC42.DLL:6663". This has happened
> on Windows 95, 98, NT4 & Me. Unfortunately I have not been able
> to duplicate the problem on numerous machines. It is an app
> that uses the IE control. I have told our users to upgrade
> to IE 5.5, but that hasn't fixed the problem. The NT 4 users
> have upgraded to service pack 6a but that didn't help them either.
> When the app was statically linked of course this wasn't a problem,
> but it introduced a whole host of other platform type issues, given
> the app was compiled on NT4.0.

> I tried quikviewing mfc42.dll on my machine, but couldn't see
> any exports with an address of 6663 (decimal, or converted to hex).
> I quikviewed my app, and it didn't show any imports at all, apart
> from the dll I wrote.

> How do I find out what the imported function is that it is failing
> on, and then what do the users of the various OSes need to install
> to update themselves? Should I just distribute the mfc42.dll I have
> on my machine (probably the one that came with sp4 of vis c++)? Will
> that be ok for all operating systems, or is there a slightly diff
> version of it for nt, 9x, me, 2000 etc?

> Thanks

> --
> Chris Cheshire

> Hi...
>             The MFC42.DLL should have a Product Version greater than
> 6.0.400.

>             Take a look at

> http://support.microsoft.com/servicedesks/fileversion/dllinfo.asp?sd=...

> Cheers
> Check Abdoul
> -------------------

> > I have written a program that is dynamically linked to the mfc
> > libraries. Some of our users have complained that it is giving the
> > error "Linked to missing export MFC42.DLL:6663". This has happened
> > on Windows 95, 98, NT4 & Me. Unfortunately I have not been able
> > to duplicate the problem on numerous machines. It is an app
> > that uses the IE control. I have told our users to upgrade
> > to IE 5.5, but that hasn't fixed the problem. The NT 4 users
> > have upgraded to service pack 6a but that didn't help them either.
> > When the app was statically linked of course this wasn't a problem,
> > but it introduced a whole host of other platform type issues, given
> > the app was compiled on NT4.0.

> > I tried quikviewing mfc42.dll on my machine, but couldn't see
> > any exports with an address of 6663 (decimal, or converted to hex).
> > I quikviewed my app, and it didn't show any imports at all, apart
> > from the dll I wrote.

> > How do I find out what the imported function is that it is failing
> > on, and then what do the users of the various OSes need to install
> > to update themselves? Should I just distribute the mfc42.dll I have
> > on my machine (probably the one that came with sp4 of vis c++)? Will
> > that be ok for all operating systems, or is there a slightly diff
> > version of it for nt, 9x, me, 2000 etc?

> > Thanks

> > --
> > Chris Cheshire