This documentation is archived and is not being maintained.
Storing Outlook Items
|Outlook Developer Reference|
This topic describes how Outlook items are stored in folders and stores based on an account in the current profile.
The Outlook object model provides the following objects to store Outlook items:
- The Folder object, which represents a container for other Folder objects and Outlook items.
Note The Folder object has replaced the MAPIFolder object that existed in Microsoft Office Outlook 2003 and earlier versions of Outlook. Although existing solutions that use the MAPIFolder object will continue to run in Microsoft Office Outlook 2007, new solutions should only use Folder.
- The Folders collection, which represents all the Folder objects at one level of the folder tree in a store. The Folders collection can also represent a collection of search folders.
Note Although a search folder is represented programmatically by a Folder object, not all events, methods, and properties of Folder apply to search folders.
- The Store object, which represents a file on the local computer or a network drive that stores e-mail messages and other items. If you use an Exchange server, you can have a store on the server, in an Exchange Public folder, or on a local computer in a Personal Folders File (.pst) or Offline Folder File (.ost). For a POP3, IMAP, and HTTP e-mail server, a store is a .pst file.
- The Stores collection, which represents all the stores in the current Outlook profile. A profile defines one or more e-mail accounts, and each e-mail account is associated with a server of a specific type. The type of server determines the type of the store and how e-mail and other items are delivered and stored. For example, an Exchange server stores e-mail and other items in either a .pst file or a .ost file on the local computer or a mapped network drive, and an HTTP server (such as Hotmail) stores items in a .pst file on the local computer.
The Store and Stores objects support the following:
- Enumerating folders in a store using Store.GetRootFolder and then Folder.Folders.
- Enumerating search folders in a store using Store.GetSearchFolders.
Note Since a store does not necessarily support search folders, in general, you should trap for returned errors when using Store.GetSearchFolders to obtain any search folders on a store.
- Better performance with enumerating folders. Because getting the root folder or search folders in a store requires the store to be open and opening a store imposes an overhead on performance, you can check the Store.IsOpen property before you decide to pursue the operation.
- Locating a local store (.pst or .ost) for an Exchange server, or a store (.pst) for a POP3, IMAP, or HTTP e-mail server, using the Store.FilePath property.
- Discovery of the Exchange store type and differentiation among different Exchange store types using the Store.ExchangeStoreType property.
- Additional information for an Exchange server through the Store.IsCachedExchange and Store.IsDataFileStore properties.
- The PropertyAccessor object through the Store.PropertyAccessor property, allowing access to store properties that are not exposed as explicit built-in properties in the Outlook object model.