Agree with Dave
The choice of using DAO or ADO at present is up to you, both are supported, and as far as I'm aware the next release of Office can use both libraries. In the future who knows? As Dave points out DAO is no longer being developed (some may regard that as a bonus (if there are no more changes then there is less chance to introduce new errors)
My personal guess is at some stage DAO wil be deprecated and ADO.NET will be the sole library. who knows Office 13..14 perhaps
Stuff I work on depends on its current age in the lifecycle, new stuff is ADO, older stuff is DAO and depending on how significant the changes to exisitng apps it may be ported to ADO. New modules in DAO projects are written in ADO unless the customer explicilty demands DAO.
I found the switch from DAO to ADO relatively straightforward, once the intial understanding pain was suffered.
in effect yer pays yer money, yer takes yer choice.....