attend a meeting. The user can open the message; mark it as accept, decline, or tentative, and return it to the originator. At this point, the object changes again into a MeetingResponse. Through a related method known as GetAssociatedAppointment, a user can obtain the AppointmentItem matching the MeetingItem.
Also in the CDO 1.2 calendar is the GetRecurrencePattern method, which indicates how frequently a meeting is set to occur. For a one-time meeting, a property called IsRecurring is set to false; for a recurring meeting, this property is set to true. Another property, the MeetingResponseStatus, indicates to the originator of a meeting request whether an individual has marked that request as accepted, declined, or tentative.
The MeetingItem has one method, GetAssociatedAppointment, and three properties: MeetingType, MeetingStatus, and Respond. The MeetingType property indicates whether the associated appointment is a meeting request or a meeting response. The MeetingStatus method indicates whether a meeting really is a meeting (or just an appointment), whether notice of it has been received by all invitees, and whether it has been scheduled or canceled.
The Respond method acts as kind of shortcut. That is, instead of having a MeetingItem call GetAssociatedAppointment and then respond, developers can call Respond to the MeetingItem. With this arrangement, users can respond to meeting requests programmatically.
Another major component of CDO is a set of rendering objects, which developers can use to display Exchange data in HTML format. Because they have been created in compiled MAPI c code, these objects provide a far more efficient way of coding than the alternative approach: loops created in Active Server Pages scripts. Using the CDO 1.2 rendering objects, developers can render an entire HTML page in just five lines of code—a small fraction of the code that would be required using Active Server Pages scripting.
The CDO 1.2 rendering objects also use the Active Server Response object, which renders data in the code page of the browser rather than that of the server. This makes the rendering objects crucial for developers who want to use international or foreign-language Exchange data in Web-based applications.
Microsoft Exchange Introduction to Collaboration Data Objects White Paper4