Microsoft KB Archive/897757

= How programs that were created in CDO version 1.2 or in CDO version 1.21 interact with Outlook 2003 in Cached Exchange Mode =

Article ID: 897757

Article Last Modified on 12/1/2005

-

APPLIES TO


 * Microsoft Office Outlook 2003
 * Microsoft Collaboration Data Objects 1.2
 * Microsoft Collaboration Data Objects 1.21

-





INTRODUCTION
This article describes how programs that were created in Collaboration Data Objects (CDO) version 1.2 or in CDO version 1.21 interact with Microsoft Office Outlook 2003 in Cached Exchange Mode.



How to use programs that were created in CDO version 1.2 or in CDO version 1.21 to send e-mail messages in Outlook 2003 in Cached Exchanged Mode
A program that was created in CDO version 1.2 or in CDO version 1.21 can use the Message.Send function to create and to send an e-mail message. In this case, however, Outlook 2003 in Cached Exchange Mode does not deliver the e-mail message until Outlook 2003 synchronizes with the Microsoft Exchange server. This behavior occurs even if the program that was created in CDO version 1.2 or in CDO version 1.21 uses the Session.DeliverNow method.

If Outlook 2003 is in Cached Exchange Mode, the Message.Send function queues the e-mail message for sending in the offline folder (.ost) file. The Message.Send function does not force a server connection. The e-mail message is sent only when Outlook 2003 connects to the Exchange server and synchronizes with offline content

The Session.DeliverNow method uses the MAPI spooler status object to request delivery of e-mail messages. Outlook 2003 in Cached Exchange Mode ignores this request. The methods and the functions that Outlook 2003 uses to connect to an Exchange server and to synchronize with offline content are not available for programs that were created in CDO version 1.2 or in CDO version 1.21.

This behavior is more a problem for stand-alone programs that were created in CDO version 1.2 or in CDO version 1.21 because they have no way to send e-mail messages. Therefore, we recommend that stand-alone programs that were created in CDO version 1.2 or in CDO version 1.21 use a separate profile that is configured for online mode, instead of using the default Outlook 2003 user profile.

CDO version 1.2 may not set the Content-Type charset property correctly for an e-mail message
When you use a program that was created in CDO version 1.2 or in CDO version 1.21 to set the Content-Type charset property for an e-mail message, the property does not change. If you verify the Content-Type charset property for the e-mail message, the Content-Type charset property is set to the following property:

'text/plain; charset=&quot;iso-8859-1&quot;'

For example, to set the Content-Type charset property to a Japanese (JIS) iso-2022-jp code page by using Microsoft Visual Basic 6.0, the code would look similar to the following code: oMessage.Fields(&quot;{8603020000000000C000000000000046}Content-Type&quot;).Value = &quot;text/plain; charset=&quot;&quot;iso-2022-jp&quot;&quot;&quot;

Additional query words: OL11 OL2003 C Sharp

Keywords: kbhowto KB897757

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.