>I trying my application on a different machine and I'm getting an error
>message "Link to missing export MFC42.DLL:6571"
>I need to know what dll a required for my application.
>I using VC++ version 5 and CRichEditView.

> I trying my application on a different machine and I'm getting an error
> message "Link to missing export MFC42.DLL:6571"
> I need to know what dll a required for my application.
> I using VC++ version 5 and CRichEditView.

>Thomas:

>Presumably, the MFC42.DLL on the target machine is older than the one which
>you have on your machine. I so you should either

>(a) Use static linking of MFC and CRT

>(b) Distribute your newer version of the DLL with your application. However
>you need to be careful, because some users will have a newer (VC6) version
>of the DLL and you do not want to replace it in that case. Also, MFC42.DLL
>is likely not the only DLL you will have trouble with (MSVCRT.DLL is
>another likely candidate).

>IMO, unless you have some special reason to avoid it, static linking is the
>way to go.

>HTH,

>David Wilkinson

>==========

>> I trying my application on a different machine and I'm getting an error
>> message "Link to missing export MFC42.DLL:6571"
>> I need to know what dll a required for my application.
>> I using VC++ version 5 and CRichEditView.

> David, Thanks for message

>  I don't think that I can use static link libray becuse I have only got the
> standand version of V.C 6.

> I have copied the newer version of the DLL's and now getting a message
> Failed to create empty document

> Thomas

> >Thomas:

> >Presumably, the MFC42.DLL on the target machine is older than the one which
> >you have on your machine. I so you should either

> >(a) Use static linking of MFC and CRT

> >(b) Distribute your newer version of the DLL with your application. However
> >you need to be careful, because some users will have a newer (VC6) version
> >of the DLL and you do not want to replace it in that case. Also, MFC42.DLL
> >is likely not the only DLL you will have trouble with (MSVCRT.DLL is
> >another likely candidate).

> >IMO, unless you have some special reason to avoid it, static linking is the
> >way to go.

> >HTH,

> >David Wilkinson

> >==========

> >> I trying my application on a different machine and I'm getting an error
> >> message "Link to missing export MFC42.DLL:6571"
> >> I need to know what dll a required for my application.
> >> I using VC++ version 5 and CRichEditView.

>Thomas:

>The message "failed to create empty document" has to do with the failure to
>create windows during initialization. You might try copying your versions
of
>comctl32.dll and riched32.dll (since you are using CRichEditView) to the
target
>machine also.

>David

>================

>> David, Thanks for message

>>  I don't think that I can use static link libray becuse I have only got
the
>> standand version of V.C 6.

>> I have copied the newer version of the DLL's and now getting a message
>> Failed to create empty document

>> Thomas

>> >Thomas:

>> >Presumably, the MFC42.DLL on the target machine is older than the one
which
>> >you have on your machine. I so you should either

>> >(a) Use static linking of MFC and CRT

>> >(b) Distribute your newer version of the DLL with your application.
However
>> >you need to be careful, because some users will have a newer (VC6)
version
>> >of the DLL and you do not want to replace it in that case. Also,
MFC42.DLL
>> >is likely not the only DLL you will have trouble with (MSVCRT.DLL is
>> >another likely candidate).

>> >IMO, unless you have some special reason to avoid it, static linking is
the
>> >way to go.

>> >HTH,

>> >David Wilkinson

>> >==========

>> >> I trying my application on a different machine and I'm getting an
error
>> >> message "Link to missing export MFC42.DLL:6571"
>> >> I need to know what dll a required for my application.
>> >> I using VC++ version 5 and CRichEditView.