apimagazine.blogg.se - Crystal report viewer errors

#Crystal report viewer errors install

Click to edit the macro and add or change labels. Related articles appear here based on the labels you select. Problems encountered when distributing Crystal Reports to other PCs are usually associated with the report not being compiled before distribution, or a missing Crystal.

#Crystal report viewer errors install

To solve this issue, install the UFL on all PCs using the report. If Landscape oriented report, type "SetDefaultOrientationPrinter" in Keywords field Errors can occur if a report using a UFL was distributed to a computer that does not have the UFL installed.If Portrait oriented report, type "SetDefaultPrinter" in Keywords field.File > Page Setup "No Printer" should always be checked (then the report uses the default printer to get/set margins).Be wary of this as it should be using ODBC Sometimes the Database setting is set to OLE. This will allow the report to use the relevant workstations ODBC settings (Use DSN) as can be seen within Data Sources (ODBC). Database > Set Datasource Location and ensure the DSN Default Properties: TRUE.This needs to be done as there are other changes/settings/runtimes deployed upon installation To check, go to Help > About > Setup Version If this field is blank Synergetic has not been locally installed on the machine.

Synergetic requires the build installed on the local workstation to be at least 20131114CR11R2.

Some of the areas that can contribute to Range Check Errors are. The Synergetic application does not have direct control over the printing of a crystal report. The printing is not actually a function of Synergetic as it simply calls Crystal Reports which does the preview and then it is Crystal Reports which also does the printing.

This error is more likely to be environmental, and related to settings on the specific workstation, or for a specific user. When viewing a Crystal Report a "Range Check Error" occurs: