CRYSTAL REPORTS v8.5 PATCHES & RUNTIME DISTRIBUTION - 31 JULY 2002 v2 --------------------------------------------------------------------- Compiled by IOSYS Technology Ltd - www.iosystech.co.uk 1 INTRODUCTION -------------- These files are for Crystal Reports version 8.5 and may all be freely distributed. All files have been sourced from either the Crystal Reports v8.5 CD or Crystal Decisions website. The Patches folder includes updates and additional files for a full copy of Crystal Reports. The Runtime Distribution folder includes three variations of the files that may be installed on a client PC, royalty-free, to provide runtime support for Crystal Reports. 2 PATCHES --------- 2.1 FILES cr85dev_en.zip - Developer Files Monthly Hot Fix - Published 9 July 2002 cr85main_en.zip - Main Program Monthly Hot Fix - Published 9 July 2002 dbexdrvr_en.zip - Database Export Drivers Monthly Hot Fix - Published 22 July 2002 outjoinsw.reg - registry patch, prevents outer joins for SmartWare reports so multi-table reports work - this file is also in the runtime distribution folder scr8_distr_expert.exe - Compiled Reports and Report Distribution Expert U2lcom.dll - Version 8.0.0.0 required for report distribution expert to work after applying dbexdrvr fix 2.2 HOT FIXES The 3 hot fix files cr85dev_en.zip, cr85main_en.zip and dbexdrvr_en.zip should be unzipped and installed to apply all the patches available to date for Crystal v8.5. Details of the patches included are available from the Crystal Decisions website. Note 3.3 below and the need to downgrade the u2lcom.dll dll if you use the report distribution expert. 2.3 COMPILED REPORTS AND REPORT DISTRIBUTION EXPERT The scr8_distr_expert.exe is a self extracting file that unzips to 3 files, the key one is rdwiz.exe, rdwiz should be run to add the Compile Report and Report Distribution Expert options to the foot of the Report menu in Crystal. The Report Distribution Expert is used to produce the Runtime Distribution files. Although this version had a published date of 24 May 2002 there is no change to rdwiz.exe (14 March 2000) from previous versions. If you run the dbexdrvr.zip hot fix you will need to replace the later u2lcom.dll installed in the crystal folder of the windows/winnt folder with version 8.0.0.0 included here (see Crystal support article c2011417). The steps used by IOSYS Technology to create a distribution set are given below; a. Select Report Distribution Export from the Report menu b. On the Options tab un-tick the database files used by report option tick the dlls for exporting option specify the folder you want the distribution files in click Next - answer OK to the MDAC dialog and No to the ODBC swodbc32... dialog c. On the File List tab select the three files in the list named after the report - crf, exe & rpt - click Remove and confirm click Add and select crxf_pdf.dll & crxf_rtf.dll from c:\windows\crystal\ (or equivalent) click Add and select crtslv.dll & ExportModeller.dll from c:\program files\Seagate Software\Shared\ (or equivalent) (if you wish to include a version of the ATL.DLL it should be added here - they are supplied on the Crystal CD) (if you want to support charts/graphs in your runtime distribution either ensure the report you are creating the distribution from includes graphs or manually add pg32conv.dll & sscsdk80.dll from c:\program files\Seagate Software\Shared\) d. On the third party dlls tab click Next - no files need to be added e. On the Distribution tab click the Build button and OK once it has finished successfully N.B. these steps are those used by IOSYS, you may wish to change some of the steps to suit your situation. 2.4 REGISTRY PATCH YOU MUST RUN the outjoinsw.reg patch (by double clicking on it) to add registry entries to make Crystal Reports work correctly with multiple table SmartWare reports. The entries stop Crystal trying to use outer joins, which are not supported by the SmartWare ODBC driver. This is the same file as included in the Runtime Distribution folder for client installations. 3 RUNTIME DISTRIBUTION ---------------------- 3.1 FILES outjoinsw.reg - registry patch, prevents outer joins for SmartWare reports so multi-table reports work - this file is also in the patches folder 3.2 FOLDERS Runtime - standard distribution, includes charting and all export formats (inc. pdf & rtf) Runtime inc 9x ATL - standard distribution as above + Windows 9x version of ATL.DLL Runtime inc NT ATL - standard distribution as above + Windows NT version of ATL.DLL 3.3 OVERVIEW To install Crystal Reports runtime support the following steps should be taken - default answers should be given and you should close any applications that may be using an earlier version of the runtime distribution. a. Run setup.exe from the runtime folder (see 3.4 to decide which folder should be used) - reboot if prompted - if you get a message saying msvcrt or mfc42 dlls cannot be replaced because they are in use, click ignore as they are standard dlls. b. Register two dlls crtslv & ExportModeller manually (requires v3 or above of ATL.DLL - see 3.4 below) Click Start Run and type regsvr32 (don't click OK yet) In Windows Explorer find crtslv.dll and drag and drop into the Run box after regsvr32 - probably in the system(32) folder under Windows/Winnt Click OK to register the dll Repeat for ExportModeller.dll (see Crystal support articles c2008078, c2009165, c2009297 & c2010080 for more information) c. Run the registry patch outjoinsw.reg by double clicking on it - you will need to do this again if you are installing over a previous runtime distribution. N.B. You will need to install the SmartWare ODBC driver and create the ODBC DSN to use SmartWare databases with Crystal. The steps necessary to create a report distribution are given in section 3.3 above. 3.4 ATL.DLL To register the dlls as described in step 3.3b above you must version 3.0, or above, of the ATL.DLL installed. If you have an earlier version or no version then use the Runtime inc 9xATL or Runtime inc NT ATL distribution - just run setup.exe from the relevant folder. If ATL.DLL was not installed at all you will need to register it (as described in 3.3b) before registering the other two dlls.