|
C O N N E C T I V I T Y
OpenDB
Users
Manual >>>
Open D3 to any ODBC-compliant
RDBMS.
OpenDB
is part of the OSFI (Open System File Interface) family of products.
It allows D3 to reach out and talk to any 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 part
of D3. All standard D3 methods of accessing
data can be used (i.e.: TCL, BASIC). As far as the D3
user/developer is concerned, the remote RDBMS is just another
D3 account, file or item. The integration of the
two systems is totally transparent.
The
table below illustrates the integration of the two worlds:
| Remote
RDBMS |
D3 |
| Database |
Account |
| Table |
File |
| Record |
Item |
How
does it work?
The
RDBMS must be ODBC-compliant and must have a Windows ODBC driver.
This driver is used to create the link between the Microsoft
ODBC Manager and the Remote RDBMS. The OpenDB Driver is installed
on the ODBC Manager. D3 talks to this Manager through
Super Q-pointers.
The
link is made through the Microsoft ODBC Manager. The diagram
bellow illustrates the setup. Notice that the ODBC Bridge can
be installed on the D3 server if D3 NT
is being used, 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 machine needs
to be present somewhere on the network to serve as the ODBC
Bridge.

If the
remote RDBMS is Oracle, use the D3 Oracle Gateway
product instead.
For
more information on OpenDB, please send an e-mail to connectivity@rainingdata.com.
|