Jet Data Access Objects

Jet Data Access Objects is a general programming interface for database access on Microsoft Windows systems, primarily for Jet and ACE databases.

Not to be confused with data access object.

History

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.

Design

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.

Jet

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.

ODBCDirect

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.

gollark: *Self*-repairing - going to an anvil is still a chore - and the effectiveness of repairs drops if you do them lots - and XP cost.
gollark: Slowly self-repairing pickaxes? It's nice to not have to replace your "random utility pickaxe" half the time.
gollark: I mean, sure, real life pickaxes can't magically go faster if you sprinkle redstone on them. But you can't make industrial machinery out of piles of metal bars and redstone, smelt iron using a cube made from rocks, kill giant spiders running around everywhere with your fists...
gollark: Why?
gollark: TiCon is hardly fantasy. It's just not completely realistic. Like, well, all of Minecraft.

See also

References
    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.