Microsoft KB Archive/194077

= PRB: Problems with CDO (1.x) After Upgrading to Outlook 98 or Outlook 2000 =

Article ID: 194077

Article Last Modified on 3/12/2004

-

APPLIES TO


 * Microsoft Collaboration Data Objects 1.21
 * Microsoft Collaboration Data Objects 1.2
 * Microsoft Outlook 98 Standard Edition
 * Microsoft Outlook 2000 Standard Edition

-



This article was previously published under Q194077



SYMPTOMS
After upgrading to Collaboration Data Objects (1.2, 1.21) and Outlook 98 or Outlook 2000, the following problems may occur:  The GetDefaultFolder method of the Session object may return the following error when specifying to retrieve the Calendar folder:

MAPI_E_NO_SUPPORT

 The Messages collection of any folder may return a Message object instead of a MeetingItem for a meeting request, meeting cancellation or meeting response. The GetMessage method of the Session object may return a Message object instead of a MeetingItem for a meeting request, meeting cancellation or meeting response.



CAUSE
These problems can occur if you call the Logon method of the Session object and specify a stored profile that has been used by Outlook 98 or 2000.



RESOLUTION
To successfully call the GetDefaultFolder function when specifying the Calendar folder or to return an appointment object instead of a message object where appropriate, use one of the following two methods:

Method One
Specify ProfileInfo when calling the Session.Logon method instead of specifying a stored profile.

For example: objSession.Logon ProfileInfo:= & vbLf &

Method Two
Use a separate profile for CDO (1.x) applications and another for Outlook 98 or 2000.



MORE INFORMATION
You use the ProfileInfo parameter of the Logon method to create a temporary profile for the session. CDO (1.1, 1.2, 1.21) generates a random name for the profile. For an authenticated profile, the format of the string follows:

& vbLf &

The server and mailbox names can be unresolved. Note that the mailbox name is not the messaging user's display name, but rather the alias or account name used internally by the user's organization. For example, you should use "johnd" instead of "John Doe". The profile is deleted after the logon is completed or terminated. The ProfileInfo parameter is only used by applications interfacing with Microsoft Exchange Server and no other services. The profileName parameter is ignored if ProfileInfo is supplied.

