quote:ADO is better for Access/SQL an VB.NET development it seems.
ADO was designed primarily as a set of data access classes for client/server apps enabling a connection to any backend data source with an OLE DB Provider written for it (this includes Jet). DAO can't Access data sources other than Jet in a client/server architecture without the use of pass-through queries and an ODBC driver.
Apps built on the .NET Framework employ ADO.NET, whose classes comprise the System.Data namespace. The System.Data namespace includes three "sub" namespaces that target distinct classes of data providers:
System.Data.SqlClient - The .NET Framework Data Provider for SQL Server.
System.Data.OleDb - The .NET Framework Data Provider for OLE DB. To connect to Jet from a NET app, you would use the System.Data.OleDb.OleDbConnection class to connect to the Jet OleDb provider. You can also connect to SQL Server using the OleDbConnection class, but the System.Data.SqlClient.SqlConnection class is designed for that purpose.
System.Data.Odbc - The .NET Framework Data Provider for ODBC data sources (though this set of classes was only supported in version 1.1 of the Framework.)
Yup, before too long ADO and ODBC will also be depracated to technological purgatory maintenance mode.