Part of the OSFI (Open System File Interface) family of products, OpenDB allows D3 to connect to ODBC-compliant databases. Once the connection is established between D3 and the remote database server, D3 is able to read, write and select data from the remote RDBMS as if it is a D3 file. All standard D3 methods of accessing data can be used (i.e.: TCL, BASIC, AQL, etc.). As far as the D3 user/developer is concerned, the remote RDBMS is just another D3 file with D3 items. If the remote RDBMS is Oracle, it is recommended to use the D3 Oracle Gateway product instead.
The table below illustrates the integration with an ODBC-compliant RDBMS database:
How does it work?
The RDBMS must be ODBC-compliant and must support a Windows ODBC driver. This ODBC driver is used to create the link between the Microsoft ODBC Manager and the Remote RDBMS. The OpenDB Driver is installed on the server with the ODBC Manager. D3 talks to this ODBC client through super Q-pointers.
The link is made through the Microsoft ODBC Manager. The diagram below illustrates the setup. Notice that the ODBC Bridge can be installed on the D3 server if it is a Windows environment (D3 Windows) or on the remote database server if the latter is a Windows based RDBMS. If D3 and the remote RDBMS servers are both UNIX based, a Microsoft Windows server needs to be present somewhere on the network to serve as the ODBC Bridge.
If the remote RDBMS is Oracle, for improved performance it is recommended to use the D3 Oracle Gateway product instead.
Previous versions of OpenDB documentation.