Differences between ado, oledb, ODBC, Dao, and rdo

Differences between ado, oledb, ODBC, Dao, and rdo

ODBC (Open Database Connectivity) is an integral part of the database in Microsoft's wosa (Windows Open Services Architecture). It establishes a set of specifications, it also provides a set of standard APIs for database access (application programming interfaces ). These APIs use SQL to complete most of their tasks. ODBC also provides support for the SQL language. You can directly send SQL statements to ODBC. --- The earliest appearance, but not always omnipotent.

Dao: the data access object is used to expose the Microsoft Jet Database Engine (first used for Microsoft Access and now supports other databases), and allows developers to directly connect to other databases through ODBC, directly connect to the access table. Dao is most suitable for single-system applications or local distribution in a small range. Its internal access to the Jet Database has been accelerated and optimized, and it is also very convenient to use. Therefore, if the database is an Access database and is used locally, we recommend that you use this access method-application uniqueness.

Rdo (Remote Data Objects) Remote Data Objects are an ODBC-oriented data access interface. They are combined with easy-to-use DAO styles and provide an interface, shows the underlying functions and flexibility of all ODBC databases. Although rdo is restricted in its access to jet or isam databases, it can only access relational databases through the existing ODBC driver. However, rdo has proved to be the best interface that many SQL Server, Oracle, and other large relational database developers often choose. Rdo provides more complex objects, attributes, and methods used to access stored procedures and complex result sets. --- It is undoubtedly based on ODBC

Ole db is a strategic system-level programming interface of Microsoft that is used to manage data within the entire organization. Ole db is an open specification built on the ODBC function. ODBC is specially developed to access relational databases. ole db is used to access relational and non-relational information sources, such as the host isam/VSAM and hierarchical database, email and file system storage, text, graphics, and geographic data, as well as custom business objects.
Ole db defines a set of COM interfaces, encapsulates various database management system services, and allows you to create software components to implement these services. Ole db components include data providers (including and presenting data), data users (using data), and service components (processing and transmitting data, such as query processors and cursor engines ).
Ole db interfaces help to smoothly integrate components, so that ole db Component vendors can quickly provide high-quality ole db components to the market. In addition, ole db contains a "bridge" Connecting ODBC, which provides consistent support for various ODBC relational database drivers. --- Claim to replace ODBC, but also compatible with ODBC

ADO (ActiveX Data Object) is a successor of Dao/rdo. Ado 2.0 is more functionally similar to rdo, and generally there is a similar ing between the two models. Ado "extends" the object model used by Dao and rdo, which means it contains fewer objects, more attributes, methods (and parameters), and events. As the latest database access mode, ADO is also easy to use, so Microsoft has clearly stated that it will focus on ADO in the future and will not upgrade Dao/rdo, therefore, ADO has become the mainstream of database development. Ado involves three Data Storage Methods: DSN (data source name), ODBC (open data connection), and ole db. The following routine will explain in detail the specific access implementation of these three methods. --- It can be said that it is the integration of system-level programming interfaces such as ODBC and oledb, and the upgrade of application-level programming interfaces such as Dao and rdo.