along with other names that are ambiguous because they are properties of forms, reports, sections, tables, or global names and constants from the Application object and the DAO and VBA libraries.
From Access 2000 and onward, Access has supported two different data access libraries, Data Access Objects (DAO) and Active X Data Objects (ADO).
It is a common question for budding Access developers to ask which libraries they should use.
There are several considerations but the most important thing to remember is that it is not an either/or proposition.
It is perfectly possible and possibly more desirable to mix both libraries in same application and thus leverage the best of both worlds.
The article focus more on when and why should a particular technology be used.
Note: As of Access 2007 and onward, the default data access library is named "Microsoft Access Database Engine Object Library" or ACEDAO.
Though this has different name, it is merely a newer version of DAO with support for new functionality introduced in those versions.
Unlike the case between ADO and DAO, one cannot have both ACEDAO and DAO referenced in the same application; one or other must be chosen.
Fortunately, the rest of article is relevant to both so for the rest of article, DAO will be used to refer to both DAO and ACEDAO.
It should be also noted that DAO has supported a different mode, ODBCDirect, which has been since deprecated and thus is not considered in this article.
ADO was introduced to Access originally as a replacement for DAO library and depending on which version the MDB was created in, the file may reference either DAO, ADO or both. Even without any active development, ADO has some compelling features for Access that merits its inclusion even in current development.