
                             Crystal Services

                    Copyright 1992  All Rights Reserved.


                           Crystal Reports Pro 2.0
                           =======================


INSTALLING CRYSTAL REPORTS PRO
==============================
    1) To install Crystal Reports Pro (CR/Pro), start Windows by typing:

                WIN

    2) Insert the CR/Pro  Product 1 disk in the appropriate drive.

    3) Make certain that the Windows Program Manager is active. Then,
       select the File Menu, and the Run command.

    4) When the Run dialog box appears, type:


                A:install   (if your Program disk is in drive A:)

                        or

                A:setup   (if your Program disk is in drive A:)

       and then select OK or press Enter to call up the CR/Pro
       installation program.


    5) Once the installation is complete, simply double click on the
       CR/Pro  icon.


    6) If you have any problems running CR/Pro , check for
       hints in the CR/Pro Help file.  Most of the
       configuration problems you may run into are covered in this
       file.


CONFIGURATION REQUIREMENTS FOR SQL
==================================

Crystal Services uses the Q+E driver to access  Microsoft and Sybase SQL
Server, NetWare SQL, Oracle, and Gupta SQLbase. If any of the following
files already exist on your system, Check that your CR/Pro  directory
appears in the path prior to any directory containing these programs
(otherwise you may not be able to log onto your system from CR/Pro):

   QELIB.DLL, QEUTIL.DLL, QLORA, QLSS.DLL, QLGUP.DLL, QLXQL.DLL


Microsoft and Sybase SQL Server
-------------------------------
When logging onto Sybase/SQL Server you may choose either the
Q+E  driver (select SQL Server/Sybase SQL) or the Microsoft ODBC
driver (select ODBC SQL).

Q+E  driver:
If you decide to use the Q+E  driver ,verify that your system is
configured correctly to run Windows applications. For example, ensure
that DOSNP is loaded if you run Novell or another equivalently named pipe.

ODBC driver:
If you decide to use the Microsoft ODBC driver, verify that your system is
configured correctly:

Note: The following example uses a server name of DSQUERY.

        1) Ensure that your system is configured to run Windows applications
           For example, make sure that DOSNP is loaded.

        2) a) If ODBC.INI and/or ODBCINST.INI do not exist in your Windows
              directory, copy the ODBC.INI file and/or the ODBCINST.INI file
              from the CR/Pro directory  to your Windows directory.

              The ODBC.INI file should contain the ODBC driver name:

                     ex:   Driver = C:\crw\Sqlsrvr.dll
              and the network address for the server
                     ex:   Address=\\SQLSERVER\PIPE\SQL\QUERY

              Run the Microsoft ODBC Administrator (Run ODBCADM.EXE from
              the CR/Pro Directory) to edit the ODBC.INI file
              and change the "Driver" location to the CR/Pro 
              directory and the "Address" line to your server network
              address.
              
              The data source name is also contained in the ODBC.INI
              file. The ODBC.INI shipped with CR/Pro  has
              the name set to SQL Server. This name will display in the
              list of servers from CR/Pro . You may change this
              name to your specific requirements.

           b) If the ODBCINST.INI file does not exist in your Windows
              directory copy ODBCINST.INI from the CR/Pro directory to
              your Windows directory.  The ODBCINST.INI file contains the
              Driver and Setup information:
                     [SQL Server]
                     Driver=C:\CRW\sqlsrvr.dll
                     Setup=C:\CRW\sqlsetup.dll

              Edit the ODBCINST.INI file and change the location
              to the CR/Pro  directory. 


        3) If ODBC.INI and ODBCINST.INI already exist in the
           Windows directory, verify that the dlls in the path
           are up-to-date, and, if necessary, modify the path to the
           CR/Pro  directory. Run the Microsoft ODBC
           Administrator (Run ODBCADM.EXE from the CR/Pro
          directory) to edit the ODBC.INI file.
           
        4) Ensure that the WIN.INI file is set correctly:
                     [SQLSERVER]
                     DSQUERY=DBNMP3,\\SQLSERVER\PIPE\SQL\QUERY

           where DSQUERY is the data source name contained in your
           ODBC.INI file and \\ SQLSERVER\PIPE\SQL\QUERY is your
           server network address as indicated in the ODBC.INI file.

        5) If you are using the Crystal Services' version of the ODBC
           SQLSRVR.DLL make sure that CTL3D.DLL is in your path. This
           file is required if you are connecting to Microsoft or Sybase
           SQL Server.
           
NetWare SQL
-----------
1) If you are on a network, make sure that NetWare SQL NLM is running.

2) Ensure that your system is configured to run Windows applications.
   For example, check that NSREQ or NSREQO is loaded, the Windows
   Requester Interface WXQLCALL.DLL is in your path, and that the NOVDB.INI
   file is set correctly.

3) Copy WBTRCALL.DLL from your CR/Pro directory to WBTRLOCL.DLL
   and copy your network version of WBTRCALL.DLL to the CR/Pro
   directory.


Oracle
------
If you are running an Oracle remote server you may decide to connect
via the ODBC driver (select ODBC SQL), or the Q+E  driver (select
SQL Server/Sybase SQL ). If you are running a stand alone machine and
are using Oracle, you must use the Q+E  driver and run Windows in
Standard mode only.

Q+E  driver:
If you decide to use the Q+E  driver verify that your system is
configured correctly, otherwise you may get the message
"'DLL cannot be found"'  when logging onto Oracle
from CR/Pro:

        1) Make sure that your system is configured to run Windows
           applications.
        2) a) If the QEX.INI file does not exist in your Windows directory,
              the CR/Pro  installation automatically copies the file
              to your Windows directory and to your CR/Pro directory.
              Double check that the file was copied to your Windows
              directory correctly.
           b) If the QEX.INI file already exists in your Windows directory,
              the CR/Pro  installation does not copy its QEX.INI
              file to your Windows directory. However, it does copy its
              version of QEX.INI to the CR/Pro directory for your
              information. Please ensure that the following settings are
              used in your copy of QEX.INI:
                      [QELCONNECT]
                      SQLServer=QESS
                      Oracle=QEORA
                      NetWareSQL=QEXQL
                      SQLBase=QEGUP
        3) If QEORA.DLL exists on your system, check that the directory
           containing Crystal Services' version of QLORA.DLL exists in the
           path prior to any directory containing QEORA.DLL.



ODBC driver:
If you decide to use the ODBC driver, verify that your system is configured
correctly:

Note: The following example uses a server name of DSQUERY.

        1) Refer to the Microsoft document "Oracle.txt" to ensure that you
           are running compatible versions.

        2) a) If ODBC.INI and/or ODBCINST.INI do not exist in your Windows
              directory, copy the ODBC.INI file and/or the ODBCINST.INI
              file from the CR/Pro directory to your Windows directory.

              The ODBC.INI file should contain the following information:
              
                [ORACLE]
                Driver=C:\CRW\sqora.dll

              Run the Microsoft ODBC Administrator (Run ODBCADM.EXE from
              the CR/Pro directory ) to edit the ODBC.INI file
              and change the driver and setup location to the CR/Pro
              directory.

           b) If the ODBCINST.INI file does not exist in your Windows
              directory, copy ODBCINST.INI from the CR/Pro directory to
              your Windows directory.  The ODBCINST.INI file contains the
              following information:

                [Oracle]
                Driver=C:\CRW\sqora.dll
                Setup=C:\CRW\orasetup.dll

              Edit the ODBCINST.INI file and change the location
              to the CR/Pro  Directory.

        3) If  ODBC.INI and ODBCINST.INI already exist in the
           Windows directory, verify that the dlls in the path
           are up-to-date, and, if necessary, modify the path to the
           CR/Pro directory. Run the Microsoft ODBC
           Administrator (Run ODBCADM.EXE from the CR/Pro
          directory) to edit the ODBC.INI file.


Gupta SQLbase 
-------------
Make sure that your system is configured to run Windows applications.



UPGRADING YOUR PRINT ENGINE APPLICATIONS
========================================

To enhance the power and flexibility of the CR/Pro Print Engine,
several modifications were made. For a complete listing of Print
Engine functions please see the Crystal Reports 2.0 and the CR/Pro 2.0
manuals.

The following functions have been replaced with newer, more powerful
functions:

        * PEOutputToDefaultPrinter replaced with PEOutputToPrinter
        * PEGetNFiles replaced with PEGetNTables
        * PEGetNthFileName replaced with PEGetNthTableLocation
        * PESetNthFileName replaced with PESetNthTableLocation
        * PELogOn replaced with PELogOnServer
        * PELogOff replaced with PELogOffServer


These substitutions have been made in the CRPE.H, GLOBAL.BAS and Pascal
TPU/PAS files.


Visual Basic Users
------------------
If your application uses the CR/Pro GLOBAL.BAS file, adjustments may be
required for several functions as defined constants have been added
to the GLOPBAL.BAS file ( see GLOBAL.BAS).

If you used the CRYSTAL.VBX custom control from an earlier 
version of Crystal Reports, you may receive an error indicating that a
control cannot be loaded when loading your Visual Basic form.  The error
is a result of having a newer CRYSTAL.VBX file then what your form
originally included. If you save your forms in 'Text style', which is an
option in Visual Basic, this upgrading problem will not occur.

There are two methods which can be used to adjust for the new VBX file:

Method 1 :  1) Select Continue and load the form.
            2) The Crystal Reports custom control will appear as a red
               or black box on your form. Delete this object.
            3) Remove the CRYSTAL.VBX file from your project.
            4) Add the CRYSTAL.VBX file onto you project once again.
            5) Reset the properties of the object as per your requirements.


Method 2 :  1) Select not to continue loading the form.
            2) During the CR/Pro installation a backup of the
               existing CRYSTAL.VBX file was made to a file entitled
               CRYSTAL.OLD.
               a) Rename the current CRYSTAL.VBX file to CRYSTAL.NEW.
               b) Copy CRYSTAL.OLD to CRYSTAL.VBX.
               This will have the effect of placing your original
               file back into the CR/Pro directory.
            3) Open your form in Visual Basic.
            4) Save the file in text format (Select SAVE AS and ensure that
               the Text format is ticked On).
            5) Close Visual Basic.
            6) Copy CRYSTAL.NEW to CRYSTAL.VBX (This will place
               the new copy of CRYSTAL.VBX back into the CR/Pro
               directory).
            You should now be able to open your form without any problems
            since your form is now saved in text format. All properties
            assigned to the original custom control are intact.

                                                     
ObjectVision Print Engine Applications
--------------------------------------
The SelfRegister function will continue to register the PEGetNFiles,
PEGetNthFileName, PESetNthFileName, PELogOn, PELogOff functions as the
new substitution functions documented above require the use of
"structures" which are not supported by ObjectVision.




PARADOX ENGINE CONFIGURATION
============================
This release of CR/Pro  supports the new Paradox Engine
3.0 which in turn supports Paradox 3.5, Paradox 4.0 and
Paradox for Windows databases.  Before using CR/Pro  you should run the
Paradox Engine Configuration program - PXENGCFG.EXE.  If you are
running Paradox 3.5 or earlier, choose Paradox 3.5 locking.  If you
are running Paradox 4.0 or Paradox for Windows, choose Paradox 4.0
locking.


If you are running ObjectVision (OV) with the CR/Pro Print
Engine you must make sure you are running a version of OV greater
than 2.0.  This is because ObjectVision uses the Paradox Engine too.
What can happen is that OV could load an old version of the Paradox
Engine which is incompatible with CR/Pro  2.0.  Conversely,
CR/Pro could load the new Paradox Engine which is incompatible
with OV 2.0 or lower.


MULTIPLE PARADOX.NET FILES
==========================
If you are encountering messages about multiple paradox.net files,
you should delete all Paradox.net, Pdoxusrs.net and *.lck files
and then run the configuration program again.

If you are encountering messages about not being able to log into
the network, this is because the new Paradox Engine is reading some
settings in your WIN.INI file which tell it what network type you
have installed:

[Paradox Engine]
.
.
NetType=2
.
.

In the new Paradox Engine 3.0 these settings are different.  In order
to get around this message you can set:

NetType=5

which means no network installed.  This allows CR/Pro  to run.


Btrieve 6.0
===========
In order to read Btrieve version 6.0 DDF files the following steps are
required prior to using CR/Pro :

        1) After installing CR/Pro  2.0, rename the WBTRCALL.DLL
           from the CR/Pro directory to WBTRLOCL.DLL

        2) Copy your Btrieve 6.0 version of WBTRCALL.DLL to the
           CR/Pro directory.

Without these steps CR/Pro  will not recognize your
DDF file and may report a Btrieve I/O error.


Printing color formatted fields to black & white Printers
===========================================================
If you have formatted fields or text to have "light" color attributes
and are printing to a printer which does not support color, the
fields will be printed in white. As a result the fields will appear
invisible unless the field has a background fill of a dark color.  The
"light" colors are: Silver, Lime, Yellow, Fuschia, Aqua and White.



SHARE REQUIRED
==============
If you are planning to report on Paradox databases you must
load SHARE.  This is because the Paradox Engine requires SHARE.
If you are not going to be reporting on Paradox databases, you
do not need to load SHARE.


RUNTIME AGREEMENT AND FILES
===========================
Please see the RUNTIME.TXT file which is located in your CR/Pro
directory for license agreement information and
for a listing of required files.

NEW FEATURES IN CR/PRO 2.0
===============================
The following new features have been added to CR/Pro  2.0.
For more information on these features please see the
associated topic in the Help file or manual.

New Database Support

   CR/Pro 2.0 Pro is compatible with Microsoft and Sybase SQL Server,
   Oracle, NetWare SQL, and Gupta SQLbase. You can link client/server
   tables to your dBase, Paradox or Btrieve files.

Functions

    The ability to write and include your own User Defined Functions has
    be added.  User defined functions may be compiled in any program which
    can create a DLL.  Crystal Services has tested DLLs created using
    Borland C++ 3.0 and Microsoft Visual C++ 1.0.

    Several Sample functions, including a NOW function which prints the
    current date and time, have been installed with CR/Pro 2.0  and appear
    under the Formula Functions section entitled  "Additional
    Functions".

Print Engine

    Several functions have been added to the CR/Pro Print
    Engine to enable a user to:

        - Log On or Off a SQL Server.
        - Enter a Password which may be required for a Paradox database
          file.
        - Get and Set the Report Title associated with a report
        - Set the Margin, Font, Minimum Section Height and Line Height.
        - Set the number of detail copies.
        - Set the Group Condition.
        - Set each section's format to allow users to turn sections on/off.


MANUAL CORRECTIONS
==================
Crystal Reports Professional Edition Manual

3-1  The term CRPE.BAS should be GLOBAL.BAS as the Crystal Reports
     Print Engine functions are declared in the GLOBAL.BAS file.

5-2  Same as above

5-4  To approximate the Direct Print Engine Call 'PELogOnServer'
     use the Custom Control 'Connect'property.


Crystal Reports 2.0 Manual

4-6   The term PH refers to the Page Header section. PH will appear
      as the section name for the Page Header area if the "Use short
      Section Names" is turned ON in File|Options.

5-20  If you intend to print the tutorial report to a black & white
      printer select maroon instead of fuschia. Light colors, like fuschia,
      will print as the color white if your printer does not support color.

6-128 The square button located in the print window does not close the
      print window, but rather cancels the reading process.

      To move around in the print window using the keyboard, use
      Ctrl+PgUp to move to previous page, and Ctrl+PgDn to move to the next
      page. Hitting PgUp or PgDn will move you around the current page
      only. Additionally, Esc will not close the print window.

