Jet Data Access Objects
||This article's lead section may not adequately summarize key points of its contents. (February 2016)|
DAO were originally called VT Objects. DAO 1.0 came up in November 1992. 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 was the final version developed by Microsoft. Microsoft says that DAO will not be available in its future 64-bit operating systems. Versions of the DAO library prior to 3.6 are not provided or supported in Microsoft Access 2013.
|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 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 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.