Crystal Reports

Crystal Reports layer

Translation layer

P2SEVT.DLL

Database layer

ADVAPI32.DLL

NT Event Logging API

NT Event Log

NOTE: The NT Event Log can only be reported on with the 32-bit version of Seagate Crystal Reports.

ODBC data sources

Open Database Connectivity (ODBC) is a standard developed by the Microsoft Corporation through which many different types of data can be accessed by a single application. An application need only communicate with one set of files, ODBC, to instantly be able to work with any source of data that can be accessed by ODBC.

There are hundreds of Database Management Systems (DBMS) available for personal computers, and thousands of applications that access DBMS data. Normally, a company that designs an application that accesses data, such as Seagate Crystal Reports, must develop a means for the application to communicate with each type of data that a customer might want to use. Seagate Crystal Reports does this with the databases that it can access directly.

Crystal Reports layer

ODBC Translation layer

ODBC

DBMS Translation layer

Database layer

By using the Structured Query Language (SQL) to communicate, all five layers can conveniently pass data from the database to your report.

Seagate Crystal Reports Layer

When working with ODBC data, Seagate Crystal Reports generates an SQL statement that requests the appropriate data from ODBC. The powerful SQL generator built into Seagate Crystal Reports is designed to create an SQL statement that will let the ODBC data source or ODBC itself do as much of the report generation as possible, returning only the data needed to produce the report. This SQL statement can be viewed and fine-tuned by anyone familiar with the SQL language. See How to edit an SQL query, Page 578.

ODBC Translation Layer

Seagate Crystal Reports uses the Dynamic Link Library PDSODBC.DLL to communicate with ODBC. This file is unique to the Seagate Crystal Reports environment and provides your report with access to any ODBC data source. This is the driver that actually passes data to and from ODBC.

ODBC Layer

ODBC is a set of several DLLs and INI files built into the Windows environment that act as a gateway through which database requests and data can pass. Any database file or format that is to be used via ODBC must be set up as an ODBC data source.

In 16-bit Windows (Windows 3.x), the primary Dynamic Link Libraries that make up ODBC are:

●ODBC.DLL, and

●ODBCINST.DLL.

Information about an ODBC data source is stored in:

●ODBC.INI, and

●ODBCINST.INI.

ODBC uses these files to get and use information about the data source.

In 32-bit Windows (Windows 95 and Windows NT), the ODBC DLLs are:

●ODBC32.DLL (32-bit version of ODBC.DLL),

●ODBCCP32.DLL (32-bit version of ODBCINST.DLL), and

●ODBCINT.DLL (ODBC 2.5 and later).

Although information regarding data sources is still recorded in ODBC.INI and ODBCINST.INI, 32-bit ODBC uses the Windows Registry database to retrieve information about individual data sources.

NOTE: For complete information on ODBC and the ODBC files, see the Microsoft ODBC documentation.

ODBC uses the SQL language for all transactions between Seagate Crystal Reports and ODBC. Even if the database does not normally use SQL to create and work with tables, the ODBC driver provided by the database (the DBMS translation layer) must communicate with ODBC using SQL. For most users, this feature of ODBC is transparent, but some more advanced users often take advantage of the features of the SQL language used by ODBC.

DBMS Translation (ODBC data source) Layer

This layer consists of one or more drivers provided by a DBMS that allow ODBC to communicate with the database. Seagate Crystal Reports ships with several ODBC drivers for many of the most common database formats. If you are unsure whether or not you can use an ODBC driver to access the data in your database, refer to the documentation for your DBMS application. Most DBMS applications that run on a Windows-based platform offer an ODBC driver.

When a DBMS provides an ODBC driver, it must register the driver with ODBC on the machine it has been installed on. It does this by assigning a name to the driver and recording the filename in the ODBCINST.INI file. Usually, this step is handled automatically when the DBMS application is installed on the system. However, your network system or DBMS application may require that you register the ODBC driver manually using the ODBC Setup application. For complete information on registering an ODBC driver with ODBC, refer to the documentation for your DBMS.

Once an ODBC driver is registered, you need to establish an ODBC data source using that driver. The ODBC data source is the object that you connect to when accessing data from Seagate Crystal Reports through ODBC. Data sources are recorded in the ODBC.INI file. The data source keeps track of the DBMS translation files (ODBC drivers) and, sometimes, the database itself. An ODBC data source can specify just a database format, such as Oracle, Gupta, Sybase SQL, or MS SQL Server. Some users, however, prefer to actually specify a certain database. In this case, the ODBC data source extends across both the DBMS translation layer, and the database layer.

NOTE: The diagram shown here illustrates the files required by Seagate Crystal Reports to work with databases designed using the 16-bit version of Microsoft Access 2.0. If you are using a different version of Access, refer to the Runtime File Requirements online Help (RUNTIME.HLP) for information on specific files required to open your Access data.

Access 2.0

Database

Excel

Microsoft Excel spreadsheets can be converted into databases that can be read by Seagate Crystal Reports through ODBC. In Excel 4.0 and earlier, use the Set Database command on the Data menu. In Excel 5.0 and later, use the Define command on the Insert menu|Name. Once converted, spreadsheet rows become records, and spreadsheet columns become fields. (For more information on converting your spreadsheets to database format, refer to your Excel documentation.) Once the spreadsheet is converted, you can set up an ODBC data source for the file, then select it from Seagate Crystal Reports.

NOTE: If you are using Excel 7.0 or later, you can export your spreadsheets as Access database tables, and read them from Seagate Crystal Reports as you would read other Access tables. Refer to your Excel documentation for more information.

Excel databases for 16-bit Windows environments are read through the CRXLS07.DLL translation file, for version 4.0 and earlier of Excel, or through the CRXLS507.DLL for version 5 of Excel.

These drivers are installed by Seagate Crystal Reports. ODBC can communicate with this driver to read the converted Excel spreadsheet.

Crystal Reports

If you are using a 32-bit Windows system, you can set up an ODBC data source for 32-bit Excel spreadsheets using the 32-bit DAO engine. The DAO engine is installed on your system when you install the 32-bit version of Seagate Crystal Reports. You must, however, set up an ODBC data source manually for your Excel spreadsheet. See How to set up an ODBC data source, Page 562.

Crystal Reports

Excel

Spreadsheet

INFORMIX

Seagate Crystal Reports accesses INFORMIX databases through ODBC. The INFORMIX client, called INFORMIX-NET, must be installed on your machine. Seagate Crystal Reports provides the necessary driver that ODBC uses to communicate with the INFORMIX database engine.

Crystal Reports

Crystal Reports layer

Translation layer

PDSODBC.DLL

ODBC

ODBC

ODBC,DLL

ODBCINST.DLL

DBMS Translation layer

CRINF507.DLL

Database layer

INFORMIX-NET

INFORMIX Database

NOTE: The 32-bit version of Seagate Crystal Reports provides the 32-bit ODBC driver CRINF509.DLL for reading 32-bit INFORMIX data.

SQL Databases through INTERSOLV DataDirect

There are many different SQL Database Management Systems available on the market, and most of them can be accessed through ODBC. Seagate Crystal Reports automatically installs and sets up several ODBC data sources allowing you to access many of the most popular SQL databases, including:

●Oracle

●Sybase SQL Server

●MS SQL Server

●Gupta SQLBase

●Scalable SQL

●DB2/2

●ASCII Text

NOTE: ASCII Text is not really an SQL database format, but text files can be read by Seagate Crystal Reports program using ODBC in the same way that many SQL databases are.

Seagate Crystal Reports provides the INTERSOLV DataDirect ODBC drivers for these SQL database formats. Not all SQL databases are accessed through these drivers, but, as a convenience, the program automatically sets up these drivers for you it is when installed. Seagate Crystal Reports still communicates with ODBC using the PDSODBC.DLL translation file, but the DataDirect drivers provide ODBC with easy access to the actual databases.

NOTE: If you are using an SQL database not accessed by the INTERSOLV drivers, refer to your DBMS documentation for complete information on the ODBC drivers required.

Do not confuse SQL databases with the SQL language. Structured Query Language (SQL) is a specialized computer language used to design, build, and read database files. See Using SQL and SQL databases, Page 545.

SQL databases are any collection of computer applications that depend on the SQL language for database creation and manipulation. SQL DBMS applications are usually designed to run as large client/server applications spread across a network.

To open an SQL database, ODBC uses a set of four DataDirect ODBC support drivers (these are the same for every SQL database format), a DataDirect ODBC driver specific to the database format, and the Database Communication Layer that actually communicates directly to the database file. The files provided for this DBMS translation layer are all INTERSOLV DataDirect drivers.

NOTE: ODBC does not have to use the INTERSOLV DataDirect drivers to access the SQL databases shown here. Most SQL DBMS applications provide their own ODBC drivers. However, Seagate Crystal Reports sets up the INTERSOLV drivers for you automatically.

Crystal Reports

PDSODBC.DLL Front-End Driver

Microsoft ODBC API

ODBC.DLL ODBCINST.DLL

NOTE: The 32-bit version of Seagate Crystal Reports provides 32bit INTERSOLV drivers for accessing SQL databases. These 32-bit drivers are named CR*09.DLL instead of CR*07.DLL.

As mentioned previously, Seagate Crystal Reports automatically creates several ODBC data sources for the SQL database formats supported by INTERSOLV DataDirect.

These data sources appear in the Log On Server dialog box:

●ODBC-CRDBM supports DB2/2

●ODBC-CRGUP supports Gupta

●ODBC-CROR7 supports Oracle 7

●ODBC-CRORA supports Oracle 6

●ODBC-CRSS supports MS SQL Server and Sybase SQL Server

●ODBC-CRXQL supports Scalable SQL

●ODBC-CRSYB supports Sybase System 10

INTERSOLV DataDirect Library

Instead of communicating directly with ODBC through the PDSODBC.DLL file, Seagate Crystal Reports can use the INTERSOLV DataDirect Library that ships with Seagate Crystal Reports. These front-end drivers use the ODBC standard as an underlying layer. However, instead of using PDSODBC.DLL to communicate with ODBC, Seagate Crystal Reports uses a specific PDS*.DLL file appropriate to the SQL database being accessed.

DataDirect Library vs. ODBC

The strength of the DataDirect Library over ODBC direct is mainly in its ability to pass proprietary SQL syntax to specific servers. For example, because Oracle has its own PDS driver, an SQL developer working with Oracle data is able to pass, at times, more precise SQL statements to the server. This way, SQL language features unique to a particular DBMS can be passed from Seagate Crystal Reports. When using ODBC direct, the PDSODBC.DLL is a common DLL that is used for all DBMS types, and proprietary SQL syntax based on specific servers may not be entirely possible.

DataDirect Library structure

With the INTERSOLV DataDirect Library, Seagate Crystal Reports uses an ODBC translator specific to the SQL database format being accessed. This file, in turn, communicates with the DataDirect Library. The DataDirect Library makes the final translation of the SQL statement to ODBC.

Crystal Reports

Front-End Driver

PDSORACL.DLL PDSGUPTA.SDLL PDSNETW.DLL PDSDB22.DLL PDSSYBAS.DLL

INTERSOLV Datadirect Library

CRLIB.DLL

CRGUI07.DLL CRUTL07.DLL CRFLT07.DLL CRSQL07.DLL CRMDS07.DLL CRBAS07.DLL

Database Communication layer

NOTE: The 32-bit version of Seagate Crystal Reports provides 32bit INTERSOLV drivers for accessing SQL databases. These 32-bit drivers are named CR*09.DLL instead of CR*07.DLL.

INTERSOLV DataDirect Library databases

●Oracle

●Sybase SQL Server

●MS SQL Server

●Gupta SQLBase

●Scalable SQL

●DB2/2

NOTE: The ODBC data sources that Seagate Crystal Reports installs for the INTERSOLV DataDirect Library appear in the Log On Server dialog box without the “ODBC-” prefix used by the data sources that go through ODBC direct.

Visual FoxPro

Microsoft Visual FoxPro data is accessed through ODBC, whereas FoxPro data from version 2.5 and earlier is accessed directly through the xBase engine. If you are using FoxPro version 2.5 or earlier, see dBASE, FoxPro, Clipper, Page 588.

Seagate Crystal Reports provides the ODBC driver VFPODBC.DLL to allow ODBC to work with Visual FoxPro data.

ODBC

ODBC

ODBC.DLL

OBDCINST.DLL

DBMS

VFPODBC.DLL Translation layer

Database layer

Visual FoxPro

Database

NOTE: Because the program supports the latest version of DAO, there is native support for VSFoxPro 5.0 (see DAO, Page 594).

Lotus Notes

A Lotus Notes database can be read by Seagate Crystal Reports through ODBC. The Lotus Notes DBMS translation layer consists of three files:

1.NOTESSQL.DLL

2.NSQLODBC.DLL

3.NSQLCFG.DLL

These files use the drivers installed by the Lotus Notes Workstation to work with the Lotus Notes database. The Workstation component of Lotus Notes must be installed on the local machine.

Crystal Reports

Crystal Reports layer

Translation layer

PDSODBC.DLL

ODBC

ODBC

ODBC.DLL

ODBCINST.DLL

DBMS Translation layer

NOTESSQL.DLL

NSQLODBC.DLL

NSQLCFG.DLL

Database layer

Lotus Notes Workstation

Lotus Notes Database