Now, apply the Root Domain Name of your AD to the proper format that the ADO provider for DSs needs. You need to change this name to a value specific to your implementation of AD:
strRootDomainNamingContext _
= "DC=InterKnowlogy, _
DC=com"
strLDAPServer = "<" & _
"LDAP://" & _
strRootDomainNamingContext _
& ">"
This ADO provider for DSs lets you define the scope of your search. DSs such as AD are hierarchical. The choices are base, oneLevel, and subTree. Our AD is small, so we use the code
sDepth = "subTree"
to search the entire subtree. In large implementations, you might want to limit the scope of your search to one level to avoid potential latency problems.
Next, execute this command to get the recordset:
ocommand.CommandText = _
strLDAPServer & ";" & _
sFilter & ";" & FieldList _
Set rs = ocommand.Execute
Now that you have a recordset, you can iterate through it to display the results. In Web Listing 1, notice how we display the Last Name and First Name of the employee but href the email address. Href calls email.asp, which Web Listing 2 shows. Email.asp lets you email a person straight from your WAP device. Also notice in Web Listing 1 how we display the mobile telephone number with an href. Here, href executes call.asp, which Listing 2 shows. Call.asp makes the call for you by dialing the phone number. Figure 7 shows the results of call.asp.
Next Month
You learned how WAP technology allows anytime, anyplace, and anywhere access to information by using existing wireless devices and with little development effort or costs. Next month, I'll examine the configuration of IIS for Microsoft SQL Server access—specifically, how to leverage the power of SQL Server in HTML and ASP on IIS.
End of Article
Prev. page
1
2
[3]
next page -->
