Share via


Property Names and the Exchange OLE DB Provider

Property Names and the Exchange OLE DB Provider

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.

When you access item properties using the server-side Exchange OLE DB (ExOLEDB) provider, you construct the property names by combining the namespace Uniform Resource Identifier (URI) and the local name, as shown in the following table.

Namespace URI Local name Full name
DAV: contentclass DAV:contentclass
urn:schemas:mailheader: to urn:schemas:mailheader:to
https://schemas.microsoft.com/ exchange/security/ descriptor https://schemas.microsoft.com/ exchange/security/descriptor
urn:schemas-microsoft- com:office:office Author urn:schemas-microsoft- com:office:office#Author

When combining the namespace URI and the local name to form the full name, the following rules are used to determine the separation character:

  1. If the namespace ends with the character '/', ':', or '?', the two parts of the name are simply joined; for example, "DAV:" + "contentclass" gives "DAV:contentclass".
  2. Otherwise, the "#" character is appended to the namespace URI and is used to separate the namespace URI from local name. For example, "urn:schemas-microsoft-com:office:office" + "Author" gives "urn:schemas-microsoft-com:office:office#Author". Adding "urn:schemas-domain-tld#" + "casenumber" yields "urn:schemas-domain-tld##casenumber".

The reverse of these rules are used to separate a namespace from a local name when transmitting properties using the WebDAV protocol.

Full names are used regardless of whether you are requesting access to the property through a Structured Query Language (SQL) statement, a Microsoft® ActiveX® Data Objects (ADO) Fields collection, or an OLE DB IRow or IRowset interface.

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.