FIX: Incorrect Return Values from COleDateTime Members

• The Microsoft Foundation Classes (MFC) included with: - Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2

SYMPTOMS

When you call the COleDateTime members (SetDate, SetTime, and SetDateTime), the return value indicates failure even though the call is successful. This may cause code that checks the return value to believe incorrectly that the call failed.

CAUSE

This behavior is caused by a problem in the COleDateTime code. COleDateTime defines the following enumeration:

    enum DateTimeStatus
    {
        valid = 0,
        invalid = 1,    // Invalid date (out of range, etc.)
        null = 2,       // Literally has no value
    };

'valid' if successful. However 'valid' is defined to be 0 in the

RESOLUTION

Call COleDateTime::GetStatus after each call to SetDate, SetTime, or SetDateTime. Then compare the value returned by GetStatus() against 'valid' to check for success. The "More Information" section of this article provides an example.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in the Visual C++ 4.2b technology update.

MORE INFORMATION

Because of the problem outlined previously in this article, code that checks the return value from these functions may believe that a failure has occurred when in fact the Date/Time was set correctly. For example, the following code will ASSERT even though the call was successful:

   COleDateTime myodt;
   VERIFY(myodt.SetDateTime(96,1,1,10,45,0));

    COleDateTime myodt;
    myodt.SetDateTime(95,6,1,23,45,0);

    VERIFY(myodt.GetStatus() == COleDateTime.valid);

Keywords          : MfcOLE vcbuglist400 vcfixlist420 kbprg kbbuglist kbfixlist
Technology        : kbMfc
Version           : 4.0 4.1 4.2
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix