Article ID: 308044 - View products that this article applies to.
This article was previously published under Q308044
This article has been archived. It is offered "as is" and will no longer be updated.
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:
(http://support.microsoft.com/kb/840667/ )You receive unexpected errors when using ADO and ADO MD in a .NET Framework application
This article provides a roadmap for learning and mastering how to use ActiveX Data Objects (ADO) via Component Object Model (COM) Interop on the Microsoft .NET platform. Roadmap articles provide links to useful information, including online documentation, Microsoft Knowledge Base (KB) articles, and white papers to assist you with learning a Microsoft product or technology.
This article contains the following sections:
Key ConceptsFor more information about key concepts, see the following Microsoft Web sites:
General ADO Overview:Help topic: COM Interop Part 1: C# Client Tutorial
General ADO Documentation:
ADO Rocks and Rolls in .NET:
Revisiting the Use of ADO in .NET Applications:
How TosFor how-to information, see the following resources:
Help topic: Accessing an ADO Recordset or Record from ADO.NET
Help topic: ADO Type mapping to .NET Framework Type
Help topic: Filling a DataSet with an ADO Recordset or Record
Quick Start: ADO Interoperability Technology Sample
The following sample illustrates how to retrieve data via an ADO Recordset on an ASPX page.
NOTE: The following path may be different, depending on where you installed the Microsoft .NET Framework Solution Developer Kit (SDK):
TroubleshootingIf you encounter problems and need answers to your questions, it is recommended that you refer to the Microsoft Newsgroups, where you can share your experiences with your peers, or the Microsoft Knowledge Base, where you can search for articles about specific issues.
Microsoft ADO .NET public newsgroup:
Search the Knowledge Base online:Use the following keywords in your search to narrow the scope to ADO via COM Interop:
kbADONET kbInterop kbADO
MSDN .NET site:
Data access technologies Web site:Another useful method for learning and troubleshooting is first to verify that the ADO code works in Visual Basic 6, and then open the Visual Basic 6 project in Visual Studio .NET. The Upgrade Wizard creates a new Visual Basic .NET project that contains the converted ADO code.
Microsoft Universal Data Access (MDAC) Web page
Migration to ADO.NETFor information about migrating to ADO.NET, see the following:
Help topic: Comparison between ADO and ADO.NET
ADO.NET for the ADO programmer:
For more information about the training that is available for Microsoft .NET technologies, see the following Microsoft Web site: