Article ID: 835428 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
If you develop a Microsoft Foundation Classes (MFC) application by using Microsoft Visual Studio .NET 2003, and the application contains OLE components, all the components may not register successfully if one of the components has a NULL PROGID parameter. This problem may cause unexpected behavior when you run the application because component information may not appear in the registry.
When the IMPLEMENT_OLECREATE macro registers the components in an MFC application, if the value that is passed for the external_name parameter is NULL, the next call to the UpdateRegistry function returns FALSE and the UpdateRegistry function does not update the component information in the registry. This behavior causes MFC to abort the registration process. Therefore, information about the other components in the application is not updated in the registry.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET 2003 service pack that contains this hotfix.
To resolve this problem immediately, 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=supportNote 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.
Date Time Version Size File name -------------------------------------------------------- 28-Jan-2004 06:21 7.10.4027.0 1,060,864 Mfc71.dll 28-Jan-2004 05:38 7.10.4027.0 40,960 Mfc71chs.dll 28-Jan-2004 05:38 7.10.4027.0 45,056 Mfc71cht.dll 28-Jan-2004 05:28 7.10.4027.0 2,183,168 Mfc71d.dll 28-Jan-2004 05:38 7.10.4027.0 65,536 Mfc71deu.dll 28-Jan-2004 05:38 7.10.4027.0 57,344 Mfc71enu.dll 28-Jan-2004 05:38 7.10.4027.0 61,440 Mfc71esp.dll 28-Jan-2004 05:38 7.10.4027.0 61,440 Mfc71fra.dll 28-Jan-2004 05:38 7.10.4027.0 61,440 Mfc71ita.dll 28-Jan-2004 05:38 7.10.4027.0 49,152 Mfc71jpn.dll 28-Jan-2004 05:38 7.10.4027.0 49,152 Mfc71kor.dll 28-Jan-2004 06:07 7.10.4027.0 1,048,064 Mfc71u.dll 28-Jan-2004 05:30 7.10.4027.0 2,178,048 Mfc71ud.dll
To work around this problem, specify a non-NULL value for the external_name parameter that is passed to the IMPLEMENT_OLECREATE macro or specify a non-NULL PROGID parameter for registering your components.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 835428 - Last Review: January 17, 2015 - Revision: 2.1