Re: ADO

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 10:36:40 -0800

OLE DB is a data access paradigm designed to provide an object interface to
OLE DB data "providers". There are providers for JET, SQL Server, ODBC and
other data sources--both relational, flat and others.

ADO is not a set of controls. It has no controls. It is an object-oriented
interface to OLE DB. It is not the latest data access technology--it's
really quite old at this point. ADO.NET is the latest technology and it's
not based on OLE DB at all.
The JET engine does not generate anything. It can be accessed via DAO or via
OLE DB data providers.

The original question asked which is better: ADO or OLE DB. Unless you
program in C++, you must use ADO to access OLE DB.

hth 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Chris Chan Ying Wai" <anonymous@discussions.microsoft.com> wrote in message
news:D8216366-D865-47F6-8093-3F8A7FA8C4B7@microsoft.com...
> ADO is a set of ActiveX controls that provide programmatic access to
Microsoft's latest underlying data access technologies. ADO is based on
OLEDB. This is a defined set of interfaces that all data sources can
implement through special drivers (or providers).
> In other words, ADO gives us a standard way of managing data from all
kinds of data stores, not just relational databases. The ever-increasing
role and importance of the Internet in application development has also
driven the design concepts of ADO. It provides a range of ways that remote
data access can be achieved over the Internet, using a Web browser.
>
> ADO uses data which is provided by OLEDB. It is a mechanism that connects
requests to the physical data store.
> Where OLEDB can be generated by JET 4.0 engine, it is a database engine
that used in Microsoft Access 2000 (part of Microsoft Office) and was chosen
because it is FREE and is already installed on most versions of Windows.
>

Relevant Pages

  • Re: Need some advice on ADO .NET
    ... William (Bill) Vaughn ... .NET and am coming from a different background (PowerBuilder)? ... As the other folks have said, ADO.NET is an ... >> data access to a variety of backend data access servers and ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Recommended data access model
    ... This is from MDAC 2.8 SDK. ... "The Role of ADO in MDAC ... The Microsoft Data Access Components provide data access that is ... easy-to-use interface to OLE DB. ...
    (comp.databases.ms-access)
  • Re: Table adapter ???
    ... ADO was a lightweight COM layer built on top of OLE DB. ... ADO and OLE DB updates came in downloads of the MDAC pack (Microsoft Data ... It also came with a OLE DB provider for ODBC which meant ...
    (microsoft.public.data.ado)
  • Re: W2K to XP ADOX 2.5/2.8 problem
    ... > ds16gt.dll,Passed,,Microsoft ODBC Driver Setup Generic ... > built by: Lab06_N' Got '2.80.1022.0 ... >.030220-1508)',Microsoft Data Access - OLE DB Core Services ...
    (microsoft.public.vb.database.ado)
  • Re: ADO
    ... OLE DB, you need to usually use C++ as you are calling API's directly. ... Eventually, ADO will no longer be supported, and ADO.NET is the way forward ... >> Mike Epprecht, Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.server)
Loading