"Maileen" <Maileen@discussions.microsoft.com> wrote in message
news:F1197495-1FFF-43D1-91F6-1A1EE16656B9@microsoft.com...
> 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

"Cor Ligthert" <notmyfirstname@planet.nl> wrote in message
news:e%23m80e51EHA.1188@tk2msftngp13.phx.gbl...
> 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.
>

On Tue, 30 Nov 2004 23:31:04 -0800, "Maileen" <Maileen@discussions.microsoft.com> wrote:

> 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" <Maileen@discussions.microsoft.com> wrote in message
news:F1197495-1FFF-43D1-91F6-1A1EE16656B9@microsoft.com...
> 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

> Just a note here that this newsgroup is dedicated to *adonet* and not ado
> or oledb.

Roy Fine wrote:
> 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
>
> "Maileen" <Maileen@discussions.microsoft.com> wrote in message
> news:F1197495-1FFF-43D1-91F6-1A1EE16656B9@microsoft.com...
>
>>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
>
>