Basic Object Model

Windows Mobile 6.5
A version of this page is also available for
4/8/2010

The primary interface to the Pocket Outlook Object Model (POOM) is the Outlook Mobile application object—IPOutlookApp. This is the only POOM object that CoCreateInstance can create, with all other objects derived from it. After logging on to the application object by using IPOutlookApp::Logon, you can then create various Personal Information Manager (PIM) item objects by using IPOutlookApp::CreateItem.

A Folder object contains an IPOutlookItemCollection object, which holds a collection of Outlook items. Folders are essentially wrappers for the Contacts, Calendar, and Tasks databases. There is also an Infrared folder for transferring items over an infrared port using IFolder::SendToInfrared.

The POOM Folder implementation is a subset of the Outlook Folder object. Each item type is associated with one of the OlDefaultFolders, and users cannot create or manipulate the Folder object itself. The Folder object is provided mainly for compatibility with Outlook.

The IPOutlookItemCollection object is obtained from the Folder object by using IFolder::get_Items. An Items collection is a collection of Contact, Task, and Appointment objects. You can retrieve individual items by using IPOutlookItemCollection::Item, delete individual items by using IPOutlookItemCollection::Remove, and create individual items by using IPOutlookItemCollection::Add. With the Items collection, you can also perform basic filtering over a collection of objects by using IPOutlookItemCollection::Restrict.

You can set and retrieve Outlook item properties by using the get/put property methods associated with each Outlook item type.

Task and Appointment items support the IRecurrencePattern object. With this object, you can set up a recurrence for a Task or Appointment. Appointment items also support the IRecipients collection, with which you can specify Meeting Recipients. An Appointment item that has a collection of Recipients, is also called a Meeting.

For more information, see The Outlook Object Model.

Community Additions

Show: