This article was previously published under Q314378
Caution ADO and ADO MD have not been fully tested in a Microsoft .NET Framework environment. They may cause intermittent issues, especially in service-based applications or in multithreaded applications. The techniques that are discussed in this article should only be used as a temporary measure during migration to ADO.NET. You should only use these techniques after you have conducted complete testing to make sure that there are no compatibility issues. Any issues that are caused by using ADO or ADO MD in this manner are unsupported. For more information, see the following article in the Microsoft Knowledge Base:
840667 (http://support.microsoft.com/kb/840667/) You receive unexpected errors when using ADO and ADO MD in a .NET Framework application
For a Microsoft Visual C# .NET version of this
article, see
310203 (http://support.microsoft.com/kb/310203/).
On This Page
INTRODUCTION
This article describes how to use Microsoft Collaboration
Data Objects (CDO) for the Microsoft Exchange 2000 Server Library (CDOEX) to enumerate all fields
of an object in Microsoft Visual Basic .NET.
Note To make sure that the code works correctly, you must run the code on an Exchange Server.
This article assumes that you are
familiar with the following topics:
•
Microsoft Exchange OLE DB (ExOLEDB) provider
•
Programming with ActiveX Data Objects Library
The following list outlines the
recommended hardware, software, network infrastructure, and service packs that
you need:
•
Microsoft Visual Studio .NET
•
Microsoft Exchange 2000 Server
To create a sample that lists all fields of an object, follow these steps:
1.
Start Visual Studio .NET.
2.
On the File menu, click New, and then click Project.
3.
Under Visual Basic Projects types, click Console Application.
By default, Module1.vb is created.
4.
Add a reference to the Microsoft CDO for Exchange 2000 Library. To do this, follow these steps:
a.
On the Project menu, click Add Reference.
b.
On the COM tab, click Microsoft CDO for Exchange 2000 Library, and then click Select.
c.
In the Add References dialog box, click OK to accept your selections.
d.
Click Yes if you receive a message to
generate wrappers for the libraries that you selected.
5.
Repeat the previous steps to add a reference to the Microsoft ActiveX Data Objects 2.5 Library.
6.
Replace all the code in the code window with the following code:
Module Module1
Sub Main()
Dim oCn As ADODB.Connection = New ADODB.Connection()
Dim oRc As ADODB.Record = New ADODB.Record()
Dim oFields As ADODB.Fields
Dim oField As ADODB.Field
' TODO: Replace with your object URL (folder or item).
Dim sFdUrl As String
sFdUrl = "http://<ExchServer>/Exchange/<UserAlias>/Inbox"
oCn.Provider = "exoledb.datasource"
oCn.Open(sFdUrl, "", "", -1)
If oCn.State = 1 Then
Console.WriteLine("Good Connection")
Else
Console.WriteLine("Bad Connection")
Return
End If
oRc.Open(sFdUrl, oCn, _
ADODB.ConnectModeEnum.adModeReadWrite, _
ADODB.RecordCreateOptionsEnum.adFailIfNotExists, _
ADODB.RecordOpenOptionsEnum.adOpenSource, _
"", "")
If oRc.State = ADODB.ObjectStateEnum.adStateOpen Then
Console.WriteLine("Record Open Success")
Else
Console.WriteLine("Record Open Fails")
Return
End If
' List all the fields.
oFields = oRc.Fields
Dim i As Integer
For i = 0 To oFields.Count - 1
oField = oFields.Item(i)
Console.WriteLine("{0} : {1}", oField.Name, oField.Value)
Next
oRc.Close()
oCn.Close()
oCn = Nothing
oRc = Nothing
oFields = Nothing
oField = Nothing
End Sub
End Module
7.
Modify the line of code that begins with TODO.
8.
Press F5 to build and to run the program.
9.
Verify that the fields of the specified object are enumerated.
Contact Microsoft Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.