The information in this article applies to:
SUMMARY
The Forward method has been added to the Collaboration Data Objects (CDO)
version 1.2 library. When you use the Forward method, it may not perform as
desired because the body of the message is not copied to the message to be
forwarded. This behavior is by design.
MORE INFORMATIONThis problem stems from the fact that the Collaboration Data Objects (CDO) library only supports non-RTF (Rich Text Format) by default, but can also be extended to support RTF. This method explicitly leaves the decision up to the developer to determine how a message is to be forwarded. NOTE: This process of copying the compressed RTF stream to the new message
also works for the CDO version 1.1 library. However, version 1.1 of the CDO
library does not support the Forward method, so a "Forward" would need to
be emulated by copying one field at a time from the fields collection of
the original message to the target message.
REFERENCESFor information on where to acquire the most recent version of the CDO library tested for client-side use, please see the following article in the Microsoft Knowledge Base: Q171440 INFO: Where to Acquire the Collaboration Data Objects LibrariesFor additional information about Collaboration Data Objects versus Active Messaging, please see the following article in the Microsoft Knowledge Base: Q176916 INFO: Active Messaging and Collaboration Data Objects (CDO) Additional query words: ActMsg OleMsg
Keywords : kbcode kbCDO120 kbCDO121 kbMsg kbVBp kbGrpMsg |
Last Reviewed: November 4, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |