REBOL / Command, which added strong encryption and ODBC access, was released in September 2000.

A Level II subscription was added in 1993, that included the MAPI, ODBC, TAPI and VFW SDKs.

* Visual C ++ 1. 5 was released in December 1993, included MFC 2. 5, and added OLE 2. 0 and ODBC support to MFC.

Although released when 16-bit 1. 5 was available, it did not include support for OLE2 and ODBC.

ODBC was later ported back to those markets, and became a de-facto standard considerably better known than CLI.

Unlike the later ODBC, Blueprint was a purely code-based system, lacking anything approximating a command language like SQL.

A proposed standard was released in December 1991, and industry input was gathered and worked into the system through 1992, resulting in yet another name change to ODBC.

ODBC 1. 0 was released in September 1992.

As MS turned its attention away from working directly on ODBC, the Unix world was increasingly embracing it.

The virtualization that ODBC offers is no longer a strong requirement, and development of ODBC is no longer as active as it once was.

In 1992, it was initially published and marketed as Microsoft's ODBC API.

Unlike relational databases, which had SQL as the standard query language, and widespread APIs such as ODBC, JDBC and OLEDB, there was no such unification in the OLAP world for a long time.

The unixODBC project was first started in the early months of 1999 ( by Peter Harvey ) and was created as at that time the developers of iODBC ( another open source ODBC implementation ) were not then willing to LGPL the code, expand the API to include the current ODBC 3 API specification, and did not consider the addition of GUI based configuration tools worthwhile.

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.

DAL's release was also coincident with Apple's fall from grace in the business world, and not coincidentally with Microsoft's ODBC efforts.

Similar in concept to ODBC, DAM saw little use and was eventually dropped in the late 1990s.

In contrast, ODBC was developed from the start to be a SQL-based system, based on the standardized Call-Level Interface from X / Open ( now part of the Open Group ).

A " classic " Mac OS version of ODBC was available for some time, although support was limited.

Microsoft originally intended OLE DB as a higher-level replacement for, and successor to, ODBC, extending its feature set to support a wider variety of non-relational databases, such as object databases and spreadsheets that do not necessarily implement SQL.

MDAC architecture may be viewed as three layers: a programming interface layer, consisting of ADO and ADO. NET, a database access layer developed by database vendors such as Oracle and Microsoft ( OLE DB,. NET managed providers and ODBC drivers ), and the database itself.

A database is not generally portable across different DBMS, but different DBMSs can inter-operate to some degree by using standards like SQL and ODBC together to support a single application built over more than one database.

* Associative arrays ( reference elements by name-MySQL & ODBC modules assign columns to named arrays )

ODBC accomplishes DBMS independence by using an ODBC driver as a translation layer between the application and the DBMS.

The later adoption of ODBC by Apple for Mac OS X 10. 4 using the standard Unix-side iODBC package further cemented ODBC as the standard for cross-platform data access.

CW 1. 0 continued the database flexibility added in CDD as well as adding an ODBC driver allowing connection to SQL databases, or any source supported by ODBC.

; odbc: Retrieves zone information from a database supported by the ODBC library

It can also link to COM components and to databases by means of ODBC.

Harbour also offers ODBC support by means of an OOP syntax, and ADO support by means of OLE.

One major difference between DAM and ODBC came about largely by accident.

Microsoft initially deprecated the MSDASQL component for their 64-bit operating systems and the Microsoft Oracle ODBC driver was later superseded by a. NET Managed Oracle Provider, which supported Oracle 9i.

The IBM System i also supports common client – server systems such as ODBC and JDBC for accessing its database from client software such as Java, Microsoft. NET languages and others.

By this time Microsoft had already granted Visigenic Software a source code license to develop ODBC on non-Windows platform.

) ODBC drivers exist for most DBMSs, including Oracle, PostgreSQL, MySQL, Microsoft SQL Server ( but not for the Compact aka CE edition ), Sybase ASE, and DB2.

* Kyle Geiger, " Inside ODBC ", Microsoft Press, 1995

* Microsoft ODBC Overview

* Microsoft ODBC & Data Access APIs History Article

Microsoft kept the API and added ODBC.

It can use MySQL, ODBC, and Microsoft SQL Server as its DBMS.

* Provide developers with the tools to port Microsoft Windows ODBC applications to other platforms with the minimum of code changes.

The 2003 Microsoft Project version employed ODBC to connect to the server, which is problematic over low bandwidth and high latency connections.

In addition it ties in seamlessly with a variety of databases includingOracle, Microsoft SQL Server, and ODBC.

There have been several deprecated components as well, such as the Microsoft Jet Database Engine, MSDASQL ( the OLE DB provider for ODBC ), and Remote Data Services ( RDS ).

The Microsoft OLE DB Provider for ODBC, or MSDASQL, was an OLE DB provider for allowing ActiveX Data Objects access to databases via any ODBC driver.

* RDO: Remote Data Objects, or RDO, was a Microsoft technology that allowed for the creation of interfaces that directly called on ODBC.

" The MDAC 1. 0 stack consisted of ODBC 3. 0, OLE DB 1. 1, ADO 1. 0, and the Advanced Data Connector ( ADC ) 1. 0 — which according to Microsoft was the precursor to the Remote Data Service of MDAC 1. 5.

* MDAC 1. 5c: fixed issues with ADO threading and ODBC Connection Pooling and was distributed via the Microsoft website.

Beginning with this version of MDAC, Microsoft Jet, Microsoft Jet OLE DB Provider, and the ODBC Desktop Database Drivers were not included.