|
Data Access |
|
MDAC (Microsoft Data Access Components) |
|
The Microsoft® Data Access Components (MDAC) SDK documents the key technologies that are part of Microsoft's strategy for providing access to information across the enterprise.
Microsoft Data Access Components include ActiveX® Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC). Data-driven client/server applications deployed over the Web or a LAN can use these components to easily integrate information from a variety of sources, both relational (SQL) and non-relational.
If you have questions or need detailed information about properly redistributing MDAC, see Redistributing MDAC for a description of the distribution requirements for MDAC.
|
Documentation:
Downloads:
|
ActiveX Data Objects (ADO) |
|
Microsoft ActiveX Data Objects (ADO) provides consistent, high-performance access to data and supports a variety of development needs, including the creation of front-end database clients and middle-tier business objects that use applications, tools, languages, or Internet browsers. The primary benefits of ADO are ease of use, high speed, low memory overhead, and a small disk footprint.
ADO provides an easy-to-use interface to OLE DB, which provides the underlying access to data. It uses a familiar metaphor — the COM Automation interface — available from all leading Rapid Application Development (RAD) tools, database tools, and languages.
|
|
Wrapper functions:
TB_ADO28
|
|
Microsoft OLE DB is a set of interfaces that expose data from a variety of relational and nonrelational sources by using the Component Object Model (COM). OLE DB interfaces provide applications with uniform access to data stored in diverse information sources. These interfaces support the amount of DBMS functionality appropriate to the data store, enabling the data store to share its data.
OLE DB comprises a programmatic model consisting of data providers, which contain and expose data; data consumers, which use data; and service components, which process and transport data (such as query processors and cursor engines). In addition, OLE DB includes a bridge to ODBC to enable continued support for the broad range of ODBC relational database drivers.
|
|
|
|
Open Database Connectivity (ODBC) |
|
The Microsoft Open Database Connectivity (ODBC) interface makes it possible for applications to access data from a variety of DBMSs. ODBC permits maximum interoperability — an application can access data in diverse DBMSs through a single interface. Furthermore, that application will be independent of any DBMS from which it accesses data. Users of the application can add software components called drivers, which create an interface between an application and a specific DBMS.
|
|
Wrapper functions:
TB_ODBC352
|
|
DAO (Data Access Objects) |
|
The DAO object model is a collection of objects that model the structure of a relational database system. With the properties and methods provided by DAO objects, you can accomplish all of the operations necessary to manage such a system, including facilities for creating databases, defining tables, fields, and indexes, establishing relations between tables, and navigating and querying the database.
The Microsoft Jet database engine translates operations on data access objects into physical operations on the database files, handling all the mechanics of interfacing with the different supported databases.
|
|
Wrapper functions:
TB_DAO36
|
|
SQL-DMO |
|
SQL Distributed Management Objects (SQL-DMO) is a collection of objects encapsulating Microsoft® SQL Server™ database and replication management.
SQL-DMO is a dual interface COM, in-process server implemented as a dynamic-link library (DLL)
SQL-DMO automates:
|
|
|
