Select the product you need help with
FIX: Microsoft Foundation Class ActiveX control that is built with Visual C++ .NET 2003 cannot be used in Visual Fox Pro 6.0Article ID: 840874 - View products that this article applies to. SYMPTOMSYou have a default Microsoft Foundation Class (MFC) ActiveX control that is built with Microsoft Visual C++ .NET 2003. You drop this form in Design mode on a Microsoft Visual Fox Pro 6.0 running form on a computer that is running Microsoft Windows 98. When you save the form, you receive the following error message:
OLE Error code 0x80004005: Unspecified error. RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
(http://support.microsoft.com/contactus/?ws=support)
Date Time Version Size File name -------------------------------------------------------- 17-Jul-2003 16:22 56,223 Afx.h 18-Apr-2004 21:56 7.10.4108.0 106,496 Atl71.dll 17-Nov-2003 21:55 17,677 Atlcomtime.inl 22-Jan-2004 12:05 13,014 Atlevent.h 18-Apr-2004 21:55 1,199,632 Atls.lib 18-Apr-2004 21:55 1,240,234 Atlsd.lib 29-Aug-2003 16:16 10,647 Atltime.h 29-Aug-2003 16:18 14,773 Atltime.inl 19-Apr-2004 06:55 319,746 Eafxis.lib 19-Apr-2004 06:55 310,120 Eafxisd.lib 11-Sep-2003 14:30 9,121 Filest.cpp 19-Apr-2004 07:40 7.10.4108.0 1,060,864 Mfc71.dll 19-Apr-2004 06:59 2,580,010 Mfc71.lib 19-Apr-2004 07:07 7.10.4108.0 40,960 Mfc71chs.dll 19-Apr-2004 07:07 7.10.4108.0 45,056 Mfc71cht.dll 19-Apr-2004 06:58 7.10.4108.0 2,183,168 Mfc71d.dll 19-Apr-2004 06:58 3,361,062 Mfc71d.lib 19-Apr-2004 07:07 7.10.4108.0 65,536 Mfc71deu.dll 19-Apr-2004 07:07 7.10.4108.0 57,344 Mfc71enu.dll 19-Apr-2004 07:07 7.10.4108.0 61,440 Mfc71esp.dll 19-Apr-2004 07:07 7.10.4108.0 61,440 Mfc71fra.dll 19-Apr-2004 07:07 7.10.4108.0 61,440 Mfc71ita.dll 19-Apr-2004 07:07 7.10.4108.0 49,152 Mfc71jpn.dll 19-Apr-2004 07:07 7.10.4108.0 49,152 Mfc71kor.dll 19-Apr-2004 07:32 7.10.4108.0 1,048,064 Mfc71u.dll 19-Apr-2004 07:03 3,348,140 Mfc71u.lib 19-Apr-2004 07:00 7.10.4108.0 2,178,048 Mfc71ud.dll 19-Apr-2004 07:01 4,287,960 Mfc71ud.lib 19-Apr-2004 07:12 555,888 Mfcs71.lib 19-Apr-2004 06:58 582,130 Mfcs71d.lib 19-Apr-2004 07:13 490,054 Mfcs71u.lib 19-Apr-2004 07:01 507,600 Mfcs71ud.lib 19-Apr-2004 06:55 16,911,250 Nafxcw.lib 19-Apr-2004 06:55 17,041,026 Nafxcwd.lib 19-Apr-2004 06:55 129,138 Nafxis.lib 19-Apr-2004 06:55 132,454 Nafxisd.lib 17-Jul-2003 16:19 6,073 Objcore.cpp 17-Jul-2003 17:21 24,323 Occcont.cpp 20-Jan-2004 13:31 16,801 Olefact.cpp 24-Mar-2004 23:32 40,431 Olepset.cpp 07-Apr-2004 16:23 13,810 Olestrm.cpp 19-Apr-2004 06:57 17,209,838 Uafxcw.lib 19-Apr-2004 06:57 17,433,082 Uafxcwd.lib 19-Apr-2004 11:02 101,376 Vc_user_atl71_rtl_x86_---.msm 19-Apr-2004 11:02 100,864 Vc_user_mfc71_loc_rtl_x86_---.msm 19-Apr-2004 11:02 919,552 Vc_user_mfc71_rtl_x86_---.msm 26-Mar-2004 20:40 19,190 Winocc.cpp STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONWhen you save a Visual Fox Pro form with an MFC ActiveX control, the IPersistStreamInit::Save interface method of the control is called. This eventually calls the AfxFullPath() function with name of the stream. In Visual C++ .NET 2002, and in earlier versions of Visual C++, this call failed on computers that were running Microsoft Windows 98. However, the failure was ignored. In Visual C++ .NET 2003, an exception is thrown. Visual Fox Pro captures the exception and displays it as the error message that is mentioned in the "Symptoms" section. REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
VS .Net 2003 MFC activex control cannot be used on VFP 6.0 form on Windows98 PropertiesArticle ID: 840874 - Last Review: May 15, 2006 - Revision: 2.0
|


Back to the top








