ado vs oledb

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I use to program using VB + ADO with MS Access.
however, i've read that oledb is faster and better then ADO to access to DB.
could you tell me in which wqy is it faster ?

what i've seen till now, it's that i need 3 times more code lines to do the
same thing.

thanks a lot,
PM
 
Maileen,

Do you mean that you have the idea that Microsoft spent money to make a
worser product than they had already with the purpose to sell less?

I do not believe that. What I have heard is that when the first locomotives
came, that there where people which told that horses were better. The most
important reason was, that they knew everything from horses and nothing from
locomotives.

That you need 3 times more code says nothing. Maybe when you are more
expirienced with that it is 3 times less.

Just my thought.

Cor
 
Maileen

OLEDB is a set of IUnknown based COM interfaces - you can access them quite
easily from VC++. ADO is a set of IDispatch interfaces - and they are
easier than OLEDB to call from VB and scripting languages.

ADO presents a subset of the OLEDB capabilities, and abstracts a lot of the
OLEDB functionality.

ADO is based on OLEDB - the two are not separate, distinct technologies.
ADO is npt measurable faster than OLEB for the majority of the things that
we do - there is still a network roundtrip and a relational database on the
other end, and those components tend to be the bottlenecks. ADO and OLEDB
are both client-side only execution units, and with 2+ ghz desktop machines,
the overhead of ADO sitting atop OLEDB is neglible.

As for the 3x more code when using OLEDB, yep - that's why ADO became such
an instant success with VB programmers - as well as VC++.

regards
roy
 
Cor Ligthert said:
Maileen,

Do you mean that you have the idea that Microsoft spent money to make a
worser product than they had already with the purpose to sell less?

I do not believe that. What I have heard is that when the first locomotives
came, that there where people which told that horses were better. The most
important reason was, that they knew everything from horses and nothing from
locomotives.

That you need 3 times more code says nothing. Maybe when you are more
expirienced with that it is 3 times less.
Click to expand...

the horses and locomotives analogu does not apply here. obviously you have
never programmed at the OLEDB interface level...

roy fine
 
Just a note here that this newsgroup is dedicated to *adonet* and not ado or
oledb.
 
Miha,
Just a note here that this newsgroup is dedicated to *adonet* and not ado
or oledb.
Click to expand...

That is why I assumed that Maileen was talking about

Ms-Access with ADO or ms-Access with OleDb in ADONET

However I can be wrong and than you are right,

Cor
 
thanks roy for your feedback. Basically i've read this information (that
OleDB is faster than ADO on MSDN delivered with VS.NET 2003)..so it's
official information from MS.
Maileen
 
Mailleen,

Now I see your other message I see that I misunderstood it.

The answer could be, when you don't need AdoNet (disconnected environment)
you can avoid it and use Ado. However with that you miss allmost all the
other benefits from AdoNet.

For me would the concurrency method be the the most important aspect to
decide in that. ADO is easy with pesimistic concurrency while AdoNet uses
optimistic concurrency.

When the last is not a problem, than in my opinion all goes for ADONET.

Sorry for misunderstanding

Cor
 
¤ Hi,
¤
¤ I use to program using VB + ADO with MS Access.
¤ however, i've read that oledb is faster and better then ADO to access to DB.
¤ could you tell me in which wqy is it faster ?
¤
¤ what i've seen till now, it's that i need 3 times more code lines to do the
¤ same thing.

I wouldn't waste much time considering this issue. If you're really concerned with performance then
use DAO for a Microsoft Access database.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top