User`s guide

Crystal Reports uses the Dynamic Link Library crdb_jdbc.dll to communicate with JDBC. This file
is unique to Crystal Reports environment and provides your report with access to any JDBC data source.
This is the driver that actually passes data to and from JDBC.
A.4.2.3 JDBC layer
JDBC acts as a gateway through which database requests and data can pass.
Note:
For more information on JDBC and the JDBC files, see the Sun Microsystems web site.
JDBC uses the SQL language for all transactions between Crystal Reports and JDBC. Even if the
database does not normally use SQL to create and work with tables, the JDBC driver provided by the
database (the DBMS translation layer) must communicate with JDBC using SQL. For most users, this
feature of JDBC is transparent, but more advanced users often take advantage of the features of the
SQL language used by JDBC.
A.4.2.4 DBMS translation (JDBC data source) layer
This layer consists of one or more drivers provided by a DBMS that allow JDBC to communicate with
the database. If you are unsure whether you can use an JDBC driver to access the data in your database,
refer to the documentation for your DBMS application.
A.4.2.5 Database layer
The database file which the JDBC data source refers to can be located anywhere on a system. Once
the JDBC data source is set up, Crystal Reports does not need to know the actual location and format
of the data. Thus, the database can have any format and can be located anywhere on a network, as
long as JDBC can communicate with it through the JDBC data source.
A.4.3 Supported JDBC database formats
There are many different SQL Database Management Systems available on the market, and many of
them can be accessed through JDBC. Crystal Reports communicates with JDBC through the
2012-03-14665
Accessing Data Sources