DAO vs ADO?

[o1110010]

being new to VBA, i recently had some questions about DAO & ADO differences. these thoughts are found in post #4 of the following thread:

http://www.access-programmers.co.uk/forums/showthread.php?t=63117

(this thread was to start a poll since i didn't see how to add a poll to the above thread. i hope i do this right... *crosses fingers*)

thanks for polling

 

[dcx693]

I started coding Access primarily using Access 97. At the time, there was no such thing as ADO, so DAO was it. Since the arrival of Access 2000, I've worked to learn ADO just as well. They are subtley different in some situations, and it can be confusing. I'd advise you to learn ADO if you only had one choice.

However, as you've probably seen in this forum (and other Access sites), plenty of databases and plenty of sample code out there still use DAO. (I've heard that because it's so "monolithic", it's just more efficient than ADO when working purely with mdb files.) It's a good idea to at least have an idea of what DAO code does so you can follow along.

 

[fuzzygeek]

DAO to ADO

The following paper in the MSDN library shows how to accomplish coding both in DAO and ADO with good examples.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndao/html/daotoadoupdate.asp

 

[o1110010]

thank you both for your replies. also thanks for some of you readers doing the poll.

that link is immense. 199 pages i believe i saw somewhere. be a tough read for me but probably my best source as of yet. thanks!