Accessing the ClearSCADA Database

In order to display ClearSCADA data in a report, the Crystal Reports application needs to access the ClearSCADA database. This access is made using an ODBC connection to the main server (see Connect to the ClearSCADA Database). You need to specify this ODBC connection for each report on your system. (If your reports include subreports, you also need to specify the relevant ODBC connection for each of those subreports.)

You also need to specify the database tables that each report and subreport is to access (see Provide Access to the Relevant Database Tables).

If a report references more than one table, you need to Specify the Links Between Multiple Tables, or Use a Subreport to Include Unrelated Data in the Same Report.

In order to reference the relevant database tables and include the required ClearSCADA data in your reports, you need to be familiar with the ClearSCADA database structure and naming conventions—this information is covered in detail in the ClearSCADA Guide to the Database. For a summary of the ClearSCADA database structure, and information on using database tables in reports, see Working with ClearSCADA Database Tables.

If required, you can include ‘custom’ database tables, such as Data Grids, in your reports (see Custom Tables and Fields). We do not recommend renaming or removing fields from a Data Grid Table that is used in a report. However, you can reflect renaming and removal changes by re-mapping the table data in the Crystal Reports application (see Map Field Changes to a Custom Table).


Disclaimer

ClearSCADA 2017 R3