There are three categories of databases accessible through DAO and the Microsoft Jet engine, as described in the following list.
Tip The ODBC API is the interface that the Microsoft Jet database engine uses to access external non-ISAM databases. Although ISAM ODBC drivers exist, Microsoft Jet uses its own installable drivers.
The Microsoft Jet database engine translates operations on DAO objects into physical operations on the database files themselves, handling all the mechanics of interfacing with the many different supported databases.
A DAO-based application uses the following operations to access a data source:
With DAO you can work directly with ISAM tables and indexes. This was an early advantage to using the DAO data access model, but ADO with OLE DB providers can also provide the same functionality.
You can use DAO to perform DDL (Data Definition Language) operations that affect the structure of your database. For example, you can create, delete, and modify the table definitions.
As an older data access technology, DAO is limited to data stores that can be handled by the Microsoft Jet engine. If your application requires access to other types of data stores, DAO cannot provide it. Additionally, DAO cannot build queries using server-side cursors. Using DAO inflicts a big performance penalty because it uses the Microsoft Jet database engine.