FIX: Message ID Changed When Checking Properties

Last reviewed: November 21, 1997
Article ID: Q176915
The information in this article applies to:
  • Collaboration Data Objects (CDO), version 1.1

SYMPTOMS

When you set a local variable equal to some of a message's properties, the message ID appears to change.

RESOLUTION

Install the new Microsoft Collaboration Data Objects 1.2 version 5.5.1664.0 or later.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft Collaboration Data Objects 1.2 version 5.5.1664.0. (Currently, this library is only available with Microsoft Exchange Server version 5.5.)

MORE INFORMATION

When you set the Sender and Recipient properties to local variables, the MessageID property of a message appears to change.

After you clear the message object (Set objOneMessage = Nothing) the MessageID property returns to its original value.

The MessageID property is not changing but Active Messaging reports a different MessageID than the actual MessageID.

REFERENCES

For additional information about Collaboration Data Objects versus Active Messaging, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q176916
   TITLE     : INFO: Active Messaging and Collaboration Data Objects (CDO)

Version           : WINDOWS:1.1
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.