Article ID: 326459 - View products that this article applies to.
This article was previously published under Q326459
This article has been archived. It is offered "as is" and will no longer be updated.
You receive an assertion in debug builds when an instance of the COleDateTime class with null status is compared with another instance with null status by using either of the following operators:
In release builds, the comparison returns an incorrect value.
This is a change in behavior from the Microsoft Foundation Classes (MFC) that is included with Microsoft Visual C++ 6.0.
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 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 fix 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 ---------------------------------------------------------- 03-Aug-2002 04:49 7.00.9524.0 974,848 Mfc70.dll 03-Aug-2002 04:49 9,554,944 Mfc70.pdb 03-Aug-2002 04:06 7.00.9524.0 1,933,312 Mfc70d.dll 03-Aug-2002 04:06 7,572,480 Mfc70d.pdb 03-Aug-2002 04:39 7.00.9524.0 964,608 Mfc70u.dll 03-Aug-2002 04:39 9,538,560 Mfc70u.pdb 03-Aug-2002 04:08 7.00.9524.0 1,925,632 Mfc70ud.dll 03-Aug-2002 04:08 7,597,056 Mfc70ud.pdb 03-Aug-2002 02:49 7.00.9524.0 84,992 Atl70.dll 03-Aug-2002 02:49 2,011,136 Atl70.pdb 03-Aug-2002 02:49 14,546 Atl.lib 03-Aug-2002 02:49 48,090 Atlmincrt.lib 03-Aug-2002 02:49 934,264 Atls.lib 19-Jul-2002 16:42 998,634 Atlsd.lib 03-Aug-2002 04:02 16,466,620 Nafxcw.lib 03-Aug-2002 04:02 16,601,214 Nafxcwd.lib 03-Aug-2002 04:05 16,741,976 Uafxcw.lib 03-Aug-2002 04:05 17,034,618 Uafxcwd.lib 03-Aug-2002 02:49 1,306,624 Atls.pdb 19-Jul-2002 16:42 1,306,624 Atlsd.pdb 03-Aug-2002 04:02 2,068,480 Nafxcw.pdb 03-Aug-2002 04:00 2,093,056 Nafxcwd.pdb 03-Aug-2002 04:04 2,068,480 Uafxcw.pdb 03-Aug-2002 04:03 2,093,056 Uafxcwd.pdb 03-Aug-2002 14:35 850,944 VC_MFC.msm 02-Aug-2002 18:01 15,737 ATLComTime.inl
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.