Jet Data Access Objects
DAO were originally called VT Objects. DAO 1.0 came up in November 1992 as part of Access 1.0. In version 3.5 it was able to bypass the Jet engine altogether and directly access ODBC data sources, including Microsoft SQL Server and other enterprise database systems. DAO 3.6 shipped with Jet 4.0. Access 2007 and later uses ACE with its ACEDAO, where most new features supported by ACE are added to. ACEDAO no longer supports ODBCDirect.
This section does not cite any sources. (November 2009) (Learn how and when to remove this template message)
DAO works by creating a "Workspace" object in which all database operations are performed. The workspace object exists as a session object that exists within a larger database engine object. There are two types of database engines: a Jet database engine object, and an ODBCDirect database engine.
The Jet database engine (in Access 2007 and later, ACE) object consists of several objects:
- a workspace object containing
- a groups-and-users object
- a database object containing objects which consist of
- containers of objects
- query definition (QueryDef) objects
- Recordset objects which are defined by a set of field objects
- relation objects which show the relationship between different fields in the database
- table definition (TableDef) objects which consists of fields and indexes of selected fields.
- a series of error objects
The first version of DAO used Snapshot/Dynaset/Table objects etc. In DAO 2.0 Recordset etc objects was introduced. DAO 3.0/3.5 only supported the old objects using a special compatibility TLB, which was removed completely in DAO 3.6.
The ODBCDirect database engine consists of a workspace object and an errors object. The main differences between this database engine and the Jet database engine are:
- the workspace object contains only a series of ODBC connection objects
- the database object consists of a series of recordset objects
The ODBC connection objects consist of QueryDef objects and recordset objects.