SUMMARY
The Active Directory Service Interfaces (ADSI) Lightweight
Directory Access Protocol (LDAP) provider implements OLE DB interfaces that
allow you to use ActiveX Data Objects (ADO) to access objects in LDAP
compliant directories. You must create an ADO connection object and set its
Provider property to "ADsDSOObject". You can specify any string, including
"", as the connection string (first argument) of the ADO connection
object's open method.
The connection object Execute method's CommandText (first object) is an
LDAP query composed of four elements separated by semicolons, in the
following format:
<LDAP://server/adsidn>;ldapfilter;attributescsv;scope
where:
- server is the name (or IP address) of the server hosting the directory.
- adsidn is the distinguished name (DN) of the starting point for your
query expressed ADsPath format with "/" separators and the root of the
namespace to the left. You can also use an X.500 style attributed name
format with the relative distinguished names separated by commas and the
root of the name space to the right.
- 1dap filter is the LDAP filter string (see rfc2254).
- attributescsv is a comma separated list of names of the attributes to be returned for each row in the recordset.
- scope is either: base, onelevel, or subtree.
NOTE: rfc2253 specifies the LDAP syntaxes on which the ADSI LDAP syntax is based.
To return the ADsPath, class, and cn attributes of all the objects in all
the recipient containers in an Exchange server, you can use the following
CommandText (in URL format):
LDAP:<//server/o=organization/ou=site/cn=recipients>;
(objectClass=*);ADsPath,objectClass,cn;subtree"
or (in attributed name format):
<LDAP://server/cn=recipients,ou=site,o=organization>, _
(objectClass=*);ADsPath,objectClass;subtree
REFERENCES
For a listing and explanation of common LDAP RFCs, including RFC 2253 and RFC 2254, please see the following article in the Microsoft Knowledge Base:
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
275917 PRB: ADSI 2.5 and MDAC 2.6 Compatibility Issues