DAO vs ADO / What are the advantages & disadvantages of each? 1

[flyover789]

Just curious to know your experience of each of the a.m technologies ...


[blue]Typos, that don't affect the functionality of code, will not be corrected.[/blue]

Martin Serra Jr.

http://www.mserrasystems.com

[blue]Shared Database_Systems and _Applications across all Business_Areas[/blue]

 

[earthandfire]

DAO is as far as I am aware optimised for Access and therefore is (at least in my opinion a better choice) if you are working with Access Tables. It is also easier with DAO to access the [internals of an Access database.

ADO is the better choice if you are accessing data external to Access.

Hope this helps.

 

[Crowley16]

ado is the standard .net odbc package designed to be compatable for all odbc connections whereas dao is specifically designed for access and the jet engine...

--------------------
Procrastinate Now!

 

[smedvid]

I've tried to standarize on ADO as a general rule, since most of my data sources are SQL Server or Oracle. Even for the few MS Access tables/databases; I am now using ADO.

Steve Medvid
"IT Consultant & Web Master"

http://www.saveourfarm.com

Chester County, PA Residents
Please Show Your Support...

 

[Ed2020]

Although ADO is now the recommended (by MS at least) method of accessing data I have spent quite some time testing the performance of ADO compared to DAO. Generally DAO is considerably faster when accessing Jet tables, so I stick with this method in MS Access unless I'm accessing Oracle data tables (which is relatively rare).

Ed Metcalfe.

Please do not feed the trolls.....

 

[lupins46]

MS say that DAO is 5 to 10 times faster than ADO for mdb tables.

 

[Ed2020]

lupins,

Do you have a URL for the article where MS confirm this? I'd like to read it....

Ed.

Please do not feed the trolls.....

 

[flyover789]

yeah, please post the link here ...

And thanks to anybody so far for your posting!

Best regards,
fly

[blue]Typos, that don't affect the functionality of code, will not be corrected.[/blue]

Martin Serra Jr.

http://www.mserrasystems.com

[blue]Shared Database_Systems and _Applications across all Business_Areas[/blue]

 

[lupins46]

I know I picked it up from a MSKB article but I don't know if I can trace it now. I'll have a look and post back later.

 

[Golom]

Look at this article under Performance.

http://support.microsoft.com/default.aspx?scid=kb;en-us;225048#XSLTH3161121122120121120120

 

[RoyVidar]

I think you may also gain or loose dependent on programming style too, but the Microsoft quote is a bit less "categoric" than the impression I'm getting through this thread. It should also be possible to find some samples where ADO is faster than DAO, or at least not slower than DAO on native tables too, here's one dating a bit

http://groups.google.com/group/microsoft.public.data.ado/browse_frm/thread/39e18dbbc0758b79/

but it's probably not dangerous to say that DAO is faster than ADO on most operations involving Jet Engine.

Another thing to think about, is that form recordset, regardless of version, are DAO, unless you're using ADP, or you've explicitly assigned an ADO recordset to the form (which can be a hassle in the 2000 version).

But what is the reason for your question? Are you thinking of converting?

If there's a (high) probability your apps will be converted to use another backend than Access, it might pay off preparing for that through for instance using ADO in stead of DAO, but then again, you will probably find lot of developers claiming that DAO is as good as ADO when connecting to SQL server, too...

Roy-Vidar