Share via



This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Microsoft® Exchange Server 2003 provides a new, high-performance OLE DB provider that you can use on the local server to access Exchange store items: the Exchange OLE DB (ExOLEDB) provider. Through the ExOLEDB provider, programmers can access the Exchange store using OLE DB, Microsoft ActiveX® Data Objects (ADO), and Collaboration Data Objects (CDO).

The following illustration shows the relationship between ADO, CDO, OLE DB, the ExOLEDB provider, and the Exchange store.

The concept art shows ADO and CDO interacting with OLE DB, OLE DB interacting with the ExOLEDB Provider, and the ExOLEDB Provider interacting with the Exchange store.

The ExOLEDB provider is a server-side component, and is therefore used only to access public stores and mailbox stores that reside on the same server. You can, however, access data on the server remotely by wrapping functionality into Component Object Model (COM) components, which can be utilized by ASP and other Web applications. The ExOLEDB provider is also ideal for use in COM+ components and Exchange store event and workflow sinks that run on the server. To access remote public stores and mailbox stores, use the WebDAV protocol, MAPI, or CDO 1.2.1.

Exchange registers this provider for the file URL namespace with the OLE DB 2.5 root binder on the local server. The root binder eliminates the requirement to explicitly specify an ADO Connection object when accessing items through OLE DB. This means that you can bind an ADO Record object directly to an item only by using a file-type URL. To bind to items by using The HTTP: URL Scheme through the ExOLEDB provider, you must specify the ExOLEDB provider binder with an ADO Connection object (Connection.Provider = "ExOLEDB.DataSource"). In most cases, it is best that you specify this provider explicitly.

Note   The Exchange Server 2003 SP2 versions of CDOEX, CDO 1.2.1, and the ExOLEDB provider handle calendar items differently than earlier versions of Exchange Server 2003. See CDOEX Calendaring Differences Between Exchange 2003 and Exchange 2003 SP2 for more information.

The following section summarizes how specific ADO objects can be used effectively in Exchange store applications:


Send us your feedback about the Microsoft Exchange Server 2003 SDK.

This topic last updated: July 2006

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.