ADO v's DAO

[gravyboy]

Quick check:

Time taken to run through 125 records in an Access DB and print one field to the immediates window...

DAO 3.51 = 190 ticks
ADO 2.1 = 480 ticks

Is this right? Have I been fed a line of crap regrading ADO or is the particular bullshit true if you think of SQL / Oracle?

------------------
Matt G
Either mattg@gravyboy.fsnet.co.uk] or matt.graveston@centrica.co.uk

[Maartin]

Just keep one thing in mind DAO has been in the game for some time now. DAO has also been designed specifically MS ACCESS, so in theory it should be faster. ADO has been designed for a Wider range of data acess types, but a lot depends on how you connect to the database you cursors etc.

Personally I still prefer DAO, easier and quicker to use.


------------------
Have Fun.
Maartin.
dinamite@onwe.co.za
-----------------------

[Enrique]

I prefer ADO, because is more flexibility than DAO,For example you can disconnect the recordset, work with it, connetcted agauin with the data base and update or insert the records, so you expend less network resources

[gravyboy]

I agree Enrique, that's the reason I'm using ADO. However as most db operations progress THROUGH the db (ie movefirst, action, <do until x> action, movenext, <loop> the loss in performance will be noticable especially if the recordsets ar large.

BTW The .updatebatch can take forever as well so including a scheduler to put this at the end of the business day might be good.

------------------
Matt G
Either mattg@gravyboy.fsnet.co.uk] or matt.graveston@centrica.co.uk

I have had much better success with DAO not only in terms of coding it but also with compatibility when installing on different systmes!

[Clunietp]

DAO is being phased out so don't make anything new with DAO. M$ future improvements will be to ADO