ICreateRow and Multiple Databases

ICreateRow and Multiple Databases

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. Each public top-level header and private mailbox is a separate database. When a Session object is created, it is always bound to only one database. Thus, it is impossible to use a single ICreateRow interface to create objects from different stores, such as an Exchange private and a public store: the ICreateRow interface is bound to a Session object which is bound to a single MDB database and logon. For each unique MDB that you connect to, you must create a Session object. This action also applies to the ICreateRow::CreateRow method and is the principal reason for the OLE DB 2.5 root binder. If the client is unsure of a URL's namespace or database origins, then the client can use a new instance of the root binder. This creates a new session and avoids any cross-database failures.

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

Build: June 2007 (2007.618.1)

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