Editing Open Database Connectivity (section)

==Bridging configurations==
A ''bridge'' is a special kind of driver: a driver that uses another driver-based technology.

===ODBC-to-JDBC (ODBC-JDBC) bridges===
An ODBC-JDBC bridge consists of an ''ODBC'' driver which uses the services of a [[JDBC type 1 driver|JDBC driver]] to connect to a database. This driver translates ODBC function-calls into JDBC method-calls. Programmers usually use such a bridge when they lack an ODBC driver for some database but have access to a JDBC driver. Examples: [https://uda.openlinksw.com/odbc-jdbc-st/ OpenLink ODBC-JDBC Bridge], [https://www.progress.com/odbc/sequelink SequeLink ODBC-JDBC Bridge].

===JDBC-to-ODBC (JDBC-ODBC) bridges===
A JDBC-ODBC bridge consists of a [[JDBC driver]] which employs an ODBC driver to connect to a target database. This driver translates JDBC [[Method (computer science)|method]] calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks a JDBC driver, but is accessible through an ODBC driver. [[Sun Microsystems]] included one such bridge in the [[JVM]], but viewed it as a stop-gap measure while few JDBC drivers existed (The built-in JDBC-ODBC bridge was dropped from the JVM in Java 8<ref>{{cite web |title=Java JDBC API |url=https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc |website=docs.oracle.com |access-date=18 December 2018 |ref=31 }}</ref>). Sun never intended its bridge for production environments, and generally recommended against its use. {{As of|2008}} independent data-access vendors deliver JDBC-ODBC bridges which support current standards for both mechanisms, and which far outperform the JVM built-in.{{Citation needed|date=July 2008}} Examples: [https://uda.openlinksw.com/jdbc-odbc-st/ OpenLink JDBC-ODBC Bridge], [https://www.progress.com/jdbc/sequelink SequeLink JDBC-ODBC Bridge], [https://zappysys.com/products/odbc-powerpack/odbc-jdbc-bridge-driver/ ZappySys JDBC-ODBC Bridge].

===OLE DB-to-ODBC bridges===
An OLE DB-ODBC bridge consists of an [[OLE DB]] Provider which uses the services of an ODBC driver to connect to a target database. This provider translates OLE DB [[Method (computer science)|method]] calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks an OLE DB provider, but is accessible through an ODBC driver. Microsoft ships one, MSDASQL.DLL, as part of the [[Microsoft Data Access Components|MDAC]] [[system component bundle]], together with other database drivers, to simplify development in COM-aware languages (e.g. [[Visual Basic]]). Third parties have also developed such, notably OpenLink Software whose 64-bit OLE DB Provider for ODBC Data Sources filled the gap when Microsoft initially deprecated this bridge for their 64-bit OS.<ref name="msdasql">''Microsoft'', "Data Access Technologies Road Map", Deprecated MDAC Components, ''Microsoft'' [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdrefodbcprovspec.asp "ADO Programmer's Guide" Appendix A: Providers, Microsoft OLE DB Provider for ODBC], retrieved July 30, 2005.  {{webarchive |url=https://web.archive.org/web/20011005101137/http://msdn.microsoft.com/library/default.asp?url=%2Flibrary%2Fen-us%2Fado270%2Fhtm%2Fmdrefodbcprovspec.asp |date=2001 October 5 }}</ref>  (Microsoft later relented, and 64-bit Windows starting with [[Windows Server 2008]] and [[Windows Vista SP1]] have shipped with a 64-bit version of MSDASQL.) Examples: [https://uda.openlinksw.com/oledb-odbc-st/ OpenLink OLEDB-ODBC Bridge] {{Webarchive|url=https://web.archive.org/web/20170327081146/https://uda.openlinksw.com/oledb-odbc-st/ |date=2017-03-27 }}, [https://www.progress.com/oledb/sequelink SequeLink OLEDB-ODBC Bridge].

===ADO.NET-to-ODBC bridges===
An ADO.NET-ODBC bridge consists of an [[ADO.NET data provider|ADO.NET Provider]] which uses the services of an ODBC driver to connect to a target database. This provider translates ADO.NET [[Method (computer science)|method]] calls into ODBC function calls. Programmers usually use such a bridge when a given database lacks an ADO.NET provider, but is accessible through an ODBC driver. Microsoft ships one as part of the [[Microsoft Data Access Components|MDAC]] [[system component bundle]], together with other database drivers, to simplify development in [[C Sharp (programming language)|C#]]. Third parties have also developed such. Examples: [https://uda.openlinksw.com/dotnet-odbc-st/ OpenLink ADO.NET-ODBC Bridge], [https://www.progress.com/net/sequelink SequeLink ADO.NET-ODBC Bridge].