ADO or DAO - I am confused (1 Viewer)

[Malcy]

Hi
About three years ago when I started doing VBA I got a drift that ADO was the way to go so have very gradually worked up my ADO skills - still not that high but with help from you guys I get by.
I recall seeing somewhere that Microsoft are moving back to DAO being default in next version of Access - which if my recall is right, suggests that they have not found ADO up to the job.
Can anyone confirm this, and should I now start trying to think in DAO rather than ADO - and do my new programming in DAO?
Would very much appreciate any views.
Thanks

 

[Summerwind]

I know how you feel. I learned ADO after becoming comfortable with DAO because ADO was to be the preferred technology for the future.

Having now heard that DAO is to become the default again, I am not too happy, especially as I'm not sure if you can manipulate Word, Excel and Outlook through DAO.

I've decided to stick with ADO unless I'm forced to change.

 

[Pat Hartman]

DAO is the native access method for Access and is the preferred method for access Access (Jet) tables. ADO is the preferred method for accessing non-Jet tables. The two are interchangeable for most things and you are unlikely to experience real timing differences with the two methods. There are some things that ADO cannot do with an Access database that DAO can do.

Even when MSFT made ADO the default library with A2K, they never actually changed Access internally so Access itself still relied on DAO for things such as form and report recordsets. With A2003, DAO is back as the default library. I strongly suggest that no matter which library you use, disambiguate all your Dim's to avoid confusion.