ۥ-x@ -]! j jj j j j j x .  B!!!!!!!!!!!!!!!.!4b!.!j .!.! Crystal Reports Technical Document Subject: Runtime Requirements for Crystal Reports 2.0(Standard) Date: July 27, 1993 Versions: 2.0(Std) Situation: As a registered user of Crystal Reports, you are allowed to distribute a runtime version of the Crystal Reports print engine with your applications at no charge. The following is an overview of runtime requirements: Solution: For all applications The following files must be included on a distribution disk, regardless of the application it accompanies: CRPE.DLL interface to the print engine COMMDLG.DLL help with printer selection, etc. CRXLATE.DLL include this file only if you are going to use the ToWords(x) or ToWords(x,#places) functions in your reports. Database specific requirements The following files are necessary for their respective databases. If your application will not be reporting on one or more of these databases then you need not include the files for the databases that will not be used: Paradox PDBPDX.DLL Crystal's Paradox DLL PXENGWIN.DLL Borland's Paradox DLL Modifications Required: A [Paradox] section in the WIN.INI file. This is created by running the PXENGWIN.EXE provided dBASE, xBase (dBase III, IV and Foxpro) PDBXBSE.DLL dBASE's DLL (all flavors) Btrieve PDBBTRV.DLL Crystal's Btrieve DLL PDCTBTRV.DLL Crystal's Btrieve DLL WBTRCALL.DLL Novell's Btrieve DLL WBTRVDEF.DLL Novell's Btrieve DLL ObjectVision PDIROV.DLL Required if you created the report by pointing to an ObjectVision OVD file If you are including a Compiled Report on the distribution diskette; include the following files: CRRUN.EXE compiled reports program .RPT your report file .MKX compiled report resources .EXE compiled report executable where is your report name NOTE: Please check your development tool's manual to see if there are additional tool specific requirements. WHERE TO INSTALL THE VARIOUS FILES CRPE files All of the print engine files should be placed in the same directory. It is required that you place these CRPE and database DLL files someplace where Windows can find them. When Windows tries to load the CRPE.DLL it will look first in the current directory, then in the \WINDOWS\ directory, then in the \WINDOWS\SYSTEM\ directory, and finally in the PATH. Report files The location you select for report files 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 any directory on the user's machine. For example: PEOpenPrintJob ("test.rpt") (No path specified) 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, then inthe Windows system directory, and finally 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 that directory as the current directory, it will find the report files. Otherwise if the path is specified: For example: PEOpenPrintJob ("c:\testdir\test.rpt") The CRPE will look only in that directory for the report. Database Files We recommend that you set the database location to be "Same as Report". 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, then in the Windows system directory, and finally 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. 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, 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. If you wish to distribute copies of the Runtime software or custom application on other terms, please contact Crystal Services directly. NOTE: Please check the manual for your development tools to see if there are additional tool--specific requirements. STDRUNT.DOC ier3b#3) O [ 13AJ[]f  * 1fiegir3579b#%3r=g) + O [ ] ? A O ֽֽ0*0*0*0* 0*0* 0* T0*0* 0* J13CqGI.0cCE,JWY[]0*0*0*0*0*0* 0*B ]u? 1f ]BTimes New Roman Symbol&Arial5Courier New 1Courier "h8jإrڅge #HH!Runtime Requirements for StandardTechnical Support Document.runtime std paradox dbase btreive objectvisionAllan D. McMordiejennifer