Article ID: 832230 - View products that this article applies to.
When you create a Microsoft Foundation Classes (MFC) application by using Microsoft Visual Studio .NET 2003, and the application uses the COleDateTime object, the COleDateTime object returns a status of Invalid for a valid date if you applied the hotfix that KB article 828100 describes to Visual Studio .NET before you created the MFC application.
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 ----------------------------------------------------------- 18-Jul-2003 00:22 56,223 Afx.h 18-Nov-2003 05:55 17,677 Atlcomtime.inl 25-Nov-2003 05:55 1,199,632 Atls.lib 25-Nov-2003 05:55 1,240,236 Atlsd.lib 30-Aug-2003 00:16 10,647 Atltime.h 30-Aug-2003 00:18 14,773 Atltime.inl 25-Nov-2003 06:44 319,746 Eafxis.lib 25-Nov-2003 06:44 310,128 Eafxisd.lib 11-Sep-2003 22:30 9,121 Filest.cpp 25-Nov-2003 07:35 7.10.3329.0 1,060,864 Mfc71.dll 25-Nov-2003 06:47 7.10.3329.0 2,183,168 Mfc71d.dll 25-Nov-2003 07:22 7.10.3329.0 1,048,064 Mfc71u.dll 25-Nov-2003 06:49 7.10.3329.0 2,178,048 Mfc71ud.dll 25-Nov-2003 07:02 555,888 Mfcs71.lib 25-Nov-2003 06:47 582,136 Mfcs71d.lib 25-Nov-2003 07:02 490,054 Mfcs71u.lib 25-Nov-2003 06:50 507,600 Mfcs71ud.lib 25-Nov-2003 06:44 16,911,008 Nafxcw.lib 25-Nov-2003 06:44 17,040,846 Nafxcwd.lib 25-Nov-2003 06:44 129,138 Nafxis.lib 25-Nov-2003 06:44 132,454 Nafxisd.lib 18-Jul-2003 00:19 6,073 Objcore.cpp 18-Jul-2003 01:21 24,323 Occcont.cpp 25-Nov-2003 06:46 17,209,828 Uafxcw.lib 25-Nov-2003 06:46 17,432,598 Uafxcwd.lib
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Article ID: 832230 - Last Review: October 25, 2005 - Revision: 1.6