DIFF BTWN ADO,DAO and RDO.

[vivek_g_r]

Dear All,

Could some one tell the differences between dao,ado and rdo.

Thanks & Regard's

R.Vivekanandaan

[MystikShadows]

Here's the explanations in chronological format.

DAO: Database Access Object came out with Visual Basic 4 today it's recommended you use ADO instead for, among other things, performance gains in most of your database operations. :-). First to come out, and slowest..correlation? I think so ;-).

RDO: Remote Database Object came out with Visual Basic 5 It was supposed to be designed to allow remote connections to other PC's database and database servers, which it did, however there was a performance cost involved (in most projects I've worked with). However it did do the job. But ADO is faster at it :-).

ADO: ActiveX Database Object. The best available to VB (aside direct ODBC which is faster) but this object hierarchy is the fastest out there and the safest for the data as well. At least it's what I've noticed. Of course other server setups might report differently ;-). but in my experience, ADO is the best of these 3 technologies.

Hope this helps

[szlamany]

This is from another post that I'm made:

DAO is a layer on top of ODBC - which is too low level (API-like) for most programmers to use directly.

OLE DB is designed to be the sucessor to ODBC - COM based. It can only really be talked to through C++, due to the complexity of the interface.

ADO is the higher-level model for talking to OLE DB.

ADO is faster and should be used at all times if possible.

And yet another post...

Here - I'll give it a try (this is right out of ADO 2.6 Programmer's Reference - by WROX publications - a truly great book).

ADO (activex data objects) and OLEDB, it's underlying technology, are going to play a big part in the future of data access. MS has unequivocally committed its future to it, and rightly so...

...Before we explain ADO...let's take a look at existing technologies...

...ODBC was the first step of the road to universal data access...ODBC was designed (by MS and other DBMS vendors) as a cross-platform, database-independent method for accessing data...through the use of an API, known as the ODBC API...

DAO (data access objects) were introduced with MS ACCESS, and provided...a set of objects...for JET and other ISAM and SQL databases...DAO also had the advantage of being able to sit on top of ODBC - allowing it to also communicate with many different databases.

...OLEDB is designed to be the successor to ODBC. Why do we need a successor - three reasons...the Internet...data being stored in a non-relational form (EXCHANGE and other file systems)...and MS desire for a COM world.

Why ADO? OLEDB is a COM-based set of object oriented interfaces...and thus...too complex...for languages other than C++. ADO is the higher-level model that most people will use. ...Equates fairly well to DAO...with methods and properties.

ADO also improves speed and ease of development by providing an object model that allows data to be retrieved...with as little as one line of code.

Hope this helps

[vivek_g_r]

Dear All,

I need a detailed explanation in this subject.

plz help me.

R.Vivek

[szlamany]

Dear All,

I need a detailed explanation in this subject.

plz help me.

R.Vivek

Tell me where you want me to give more detail - I can explain further, but it appears to me that I have covered all bases.

[szlamany]

Again, from WROX publishers - ADO 2.6 Programmers Reference:

DAO - Data Access Objects

Introduced by MS and provided a strictly hierarchical set of objects for manipulating data in JET and other ISAM and SQL databases. First available with VB3...DAO...sits on top of ODBC - this allowed it to communicate with many different databases.

RDO - Remove Data Objects

Aimed as the successor to DAO for VB programmers...is a thin layer that sits on top of ODBC, allowing better access to server databases, such as SQL Server. This brought the flexibility of ODBC with a much easier programming model than DBLib or the ODBC API...RDO and ODBC share the same relationship as ADO and OLEDB - a thin layer on top of an underlying data access mechanism.

I believe I've already talked enough about ADO and OLE DB...

[vbyogesh]

Hello
I still confuse between all these what is ADO,RDO ,DAO,
What is difference ADO AND OLEDB.WHAT IS ODBC.
plS I AM VERY NEW TO PROGRAMMING.

Thx

Yogesh

[szlamany]

Hello
I still confuse between all these what is ADO,RDO ,DAO,
What is difference ADO AND OLEDB.WHAT IS ODBC.
plS I AM VERY NEW TO PROGRAMMING.

Thx

Yogesh

ODBC is low level data access components - hard to call from VB.

OLEDB is also low level data access components - also hard to call from VB.

OLEDB is new and is designed to replace ODBC.

Since both are low level, the other interface protocols, RDO and DAO (sit on top of ODBC) and ADO (sits on top of OLEDB) are designed to allow the VB programmer to interact with the low level components more easily.