Clarion Community Help

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
| **Navigation:**  »No topics above this level«====== Crystal Reports Overview ====== | {{btn_prev_d.gif}}[[coming future.htm|{{btn_home_n.gif|Return to chapter overview}}]]{{btn_next_d.gif}} |
|  ||

Business Objects's Crystal Reports is one of the leading report writers delivering Windows reports. For more information on this product visit the Crystal Reports web site at [[http://www.businessobjects.com|www.businessobjects.com]].

Clarion's Crystal Report interface is comprised of templates, libraries, and DLLs that communicate with Crystal Reports, versions 8 or 9 (see below). The DLL is accessed by a Class Interface and is hooked to your application using simple standard Clarion code. This interface allows a seamless integration of previously defined Crystal reports within a Clarion application. The Crystal report engine accesses data and creates the report. The report can be previewed in a Clarion window.

Clarion's Crystal Reports implementation is compatible with both the ABC and Legacy templates. It can only be used in 32-bit applications.

**Crystal Reports Files**

The files that make up Clarion's Crystal Reports interface are:

Clacr8.inc   Crystal Class Definition

Clacr8L.inc   Crystal Class Definition Local Compile

Clacr8.tpl   Templates

Clacr8.lib   Crystal LIB

Clacr8L.lib   Crystal Local LIB

Clacr8.dll   Crystal DLL

**Files to Distribute**

To distribute an application that includes the Crystal Report interface, the following files must be distributed.

Clacr8.dll   Crystal DLL

This DLL file must be included in distribution when an application is compiled using the Standalone (ClaRUN.DLL) Run-Time library.

**Other Runtime Distribution Files**

According to the latest Crystal Reports documentation (Version 9), the required runtime files for an application developed using the Crystal Report Print Engine API (crpe32.dll) are listed below.

{{notebox.jpg|NoteBox.jpg}}

The Crystal Reports Print Engine is now considered a legacy API and will no longer expose calls for any the new features included in Crystal Reports. For more information, see "Retired Developer APIs" in //Crystal Reports Developer's Guide (CrystalDevHelp.chm)//.

__**File**__** **__**Developer/Distribution Locations**__**   **__**Description**__

(Locations are the same unless listed separately.)

crpe32.dll \Program Files\Common Files\Crystal Decisions\2.0\bin Interface to the Crystal Report Engine

crqe.dll \Program Files\Common Files\Crystal Decisions\2.0\bin Crystal Query Engine

Implode.dll \Program Files\Common Files\Crystal Decisions\2.0\bin Compression Library

msvcrt.dll \Windows\system32 or \WINNT\system32 (NT only) Microsoft (R) C Runtime Library

querybuilder.dll \Program Files\Common Files\Crystal Decisions\2.0\bin Crystal Query Builder

riched20.dll \Windows\system32 or \WINNT\system32 (NT only) Rich Text Edit Control, v3.0

ufmanager.dll \Program Files\Common Files\Crystal Decisions\2.0\bin Manager for loading UFL's

unicows.dll See the note below.       Unicode Layer for Win9x

usp10.dll \Windows\system32 or \WINNT\system32 (NT only) Uniscribe Unicode script processor

{{notebox.jpg|NoteBox.jpg}}

The following DLLs need only be included under these circumstances:

Include Implode.dll only for applications using reports created in versions previous to Crystal Reports 8.

Include unicows.dll only for applications installed on Win9x machines. Due to licensing restrictions, you must get unicows.dll from the Microsoft web site.

Go to http://www.microsoft.com/msdownload/platformsdk/sdkupdate/default.htm? and select "Microsoft Layer for Unicode on Windows 95/98/ME Systems (MSLU) version 1.0".

If your application uses any of the following functions,

//CrPEExportToDisk CrPEExportToExch  crPEExportToMapi//

//CrPEExportToHTML CrPEExportToODBC crPESelectPrinter//

//CrPEGetSelectedPrinter//

you must include:

crwrap32.dll \Program Files\Common Files\Crystal Decisions\2.0\bin

Print Engine Wrapper (intended as a sample of how to prototype structured calls for languages that do not support structures)

See your Crystal Reports Documentation for any additional runtime requirements.