Crystal Reports Pro Runtime Program
-----------------------------------


This text file includes a description of which files to include
on a runtime distribution disk.  It also includes the Runtime
Program License Agreement.



REQUIRED RUNTIME ENGINE FILES
-----------------------------

The following file must be included on a distribution disk:

   PRINT ENGINE
        CRPE.DLL     - interface to the print engine
        COMMDLG.DLL  - printer selection dialog


In addition, you must include the database DLL files that
are required for the databases that you wish to report on:


   PARADOX
        PDBPDX.DLL   - Crystal's Paradox DLL
        PXENGWIN.DLL - Borland's Paradox DLL

   xBASE
        PDBXBSE.DLL  - dBASE - all flavors

   Btrieve
        PDBBTRV.DLL  - Crystal's Btrieve DLL
        PDCTBTRV.DLL - Crystal's Btrieve DLL
        WBTRCALL.DLL - Novell Btrieve DLL
        WBTRVDEF.DLL - Novell btrieve DLL

   ObjectVision
        PDIROV.DLL   - Required if you created the report by
                       pointing to an ObjectVision OVD file

   SQL Server ( using Q+E driver )
        QELIB.DLL    - Q+E Database Library
        QEUTIL.DLL   - Q+E Database Library
        QLSS.DLL     - Q+E Database Library
        DBNMP3.DLL   - Sybase/SQL Server Database Library
        PDSSYBAS.DLL - Crystal's Sybase/SQL Server DLL

   Microsoft ODBC
        ODBC.DLL     - Microsoft ODBC DLL
        ODBCINST.DLL - Microsoft ODBC Install DLL
        ODBC.INI     - Microsoft ODBC INI
        ODBCINST.INI - Microsoft ODBC Install INI
        PDSODBC.DLL  - Crystal's ODBC DLL

        If you are using ODBC with SQL Server, the
        following are required:

        CTL3D.DLL    - Microsoft Control 3D DLL
        SQLSRVR.DLL  - ODBC SQL Server DLL
        SQLSETUP.DLL - ODBC SQL Server Setup DLL
        DBNMP3.DLL   - Sybase/SQL Server Database Library

        If you are using ODBC with Oracle, the following
        are required:

        ORASETUP.DLL  - Oracle setup DLL
        SQORA.DLL     - Oracle ODBC DLL

   NetWare SQL
        QELIB.DLL    - Q+E Database Library
        QEUTIL.DLL   - Q+E Database Library
        QLXQL.DLL    - Q+E Database Library
        PDSNETW.DLL  - Crystal's Netware SQL DLL

   Gupta SQLbase
        QELIB.DLL    - Q+E Database Library
        QEUTIL.DLL   - Q+E Database Library
        QLGUP.DLL    - Q+E Database Library
        PDSGUPTA.DLL - Crystal's Gupta DLL

   Oracle
        QELIB.DLL    - Q+E Database Library
        QEUTIL.DLL   - Q+E Database Library
        QLORA.DLL    - Q+E Database Library
        PDSORACL.DLL - Crystal's Oracle DLL

Again, if you are only using one type of database then you only
have to include the database DLL's for that database.


If you are including a Compiled Report on the distribution diskette
include the following files:

        CRRUN.EXE     - compiled reports program
        XXXXXXXX.RPT  - your report file
        XXXXXXXX.MKX  - compiled report resources
        XXXXXXXX.EXE  - compiled report executable

        where XXXXXXXX is your report name

        Please ensure that the .RPT, .MKX, and .EXE files are
        stored in the same directory.

If your report contains a formula which uses one of the User Defined
Functions ( a function listed in the formula editor 'Additional Functions'
section ), the associated XXXXXXXX.DLL file must be included
on the distribution diskette. If the function is one of the Crystal Reports
Pro's sample User Defined Functions, include the UFLSAMPL1.DLL file.


The following file must be included on a distribution disk if
your reports are using the ToWords function:

        CRXLATE.DLL  - ToWords function





WHERE SHOULD YOU INSTALL THE CRPE FILES?
----------------------------------------

All of the files should be placed in the same directory.  It is required
that you place these CRPE and database DLL files some place where Windows
can find them.  When Windows trys to load the CRPE.DLL it will look in the
current directory, in the Windows directory, in the Windows system
directory, and then in the path therefore you should place these files
in on of these places.





WHERE SHOULD YOU PUT YOUR REPORT FILES AND DATABASE FILES?
---------------------------------------------------------

Report files
------------
This depends on what you have specified in your application.  It
is recommended that you use the report name with no path when you
specify a report to print in your PEPrintReport or PEOpenPrintJob
calls.  If you have no path specified in your call you can install
your runtime application in whatever directory you like on the user's
machine.


No path specified in the engine call
------------------------------------
e.g.   PEOpenPrintJob ("test.rpt")

When the call is made, the print engine will look in the current
directory for the report file.  If CRPE doesn't find the report
file in the current directory, it will look for it in the Windows
directory, in the Windows system directory, and then in the path.

This means that you can place the report files in the same directory
as your application and your application can be installed in any directory
you like.  As long as the application keeps this directory as the current
directory, it will find the report files.


Path specified in the engine call
---------------------------------
e.g.  PEOpenPrintJob ("c:\testdir\test.rpt")
If you have specified a path in your call then CRPE will look
in that directory for the report.




Database Files ( PC databases only )
--------------
We recommend that you set the database location to be
"Same as Report" in the report file itself.  This will tell the CRPE
print engine to look in the same directory as the report file for the
database files.  Again, if it does not find the database files in this
directory, CRPE will look for the database files in the Windows directory,
in the Windows system directory, and then in the path.




RUNTIME SOFTWARE AND SAMPLE APPLICATION LICENSE
-----------------------------------------------


Permission is granted to the original purchaser of this Runtime package
under Crystal's copyright to reproduce and distribute exact copies of
the Runtime software, and to modify, reproduce and distribute the sample
applications, made from the original disks in this package (or a set of
backup copies made directly from them), provided that:

- Such copies are distributed with and for the purpose of executing
specific-purpose application programs written using an authorized copy
of Crystal Reports Pro.

- The user will remain solely responsible to anyone receiving such copies
for any support, service, upgrades or technical or other assistance, and
such recipients will have no right to contact Crystal for such services or
assistance.

- The runtime program will not be altered, disassembled, decompiled or
reverse-engineered.

- Crystal provides no warranty at all other than the Limited Warranty
provided in this package to the original purchaser.  The purchaser will
indemnify and hold Crystal harmless from and against any claims or
liabilities arising out of its use, reproduction or distribution and the
use by the recipients of the copies made hereunder.

- The permission granted herein is solely for the purpose of using the
Runtime program and custom applications to execute specific-purpose
application programs written using an authorized copy of Crystal Reports
Pro, and the user is not authorized to include the Runtime program or
custom applications in any general-purpose, report writing and/or
database querying product, or in any product that is otherwise generally
competitive with Crystal Reports Pro.


If you wish to distribute copies of the Runtime software or custom
application on other terms, please contact Crystal Services directly.






