لطفا منتظر باشید ...
Sources of Errors
Existing Reports
If you have existing Crystal Reports you have created using a previous version of Crystal Reports (8.5 or below) you can use these reports with Crystal Reports.NET by importing them into your project or leave them as external and reference them within your application. Below are some of the most common errors that occur with reports and Crystal Reports.NET:
Error
Interpretation
Opening a .NET report in a previous version (8.5 or below) causes a faultOnce you have saved a report in Crystal Reports.NET, the report cannot be opened in previous versions of Crystal Reports. You should keep a copy of the report if you wish to open it in a previous version.You cannot open Crystal Reports.NET reports in Crystal Reports 8.5 or below because the file format for a .NET report is different from that for previous versions.The Crystal Knowledge Base recommends two different strategies for using reports you also need to edit outside of Crystal Reports.NET:If you add the report as an Existing item and don't change the report's structures, you should be able to edit the report with the previous version designer (8.5 or below) as the report file remains in its original report format.If you know you need to edit the report outside of Crystal Reports.NET, the best method is to leave the report file alone and reference the file at run time. Rather than importing or creating a new report, you can load the previous version report file into the application at run time and view the reports. If you were to set the report source property with the path and name of the report, the report could then be viewed within your .NET application, but still be edited externally with the previous version's Report Designer.
Crystal Dictionary is not supported in this versionCrystal Reports.NET does not support Crystal Dictionaries (or Seagate Info Views) as a data source for reports. If you attempt to import an existing report that uses either of these data sources, you will receive this error message. To utilize this report, you need to either set the location of the report to a valid data source, or you could re-create the report within the Crystal Reports.NET Report Designer.
The formatting of graphs is lost in Crystal Reports.NETWhen importing a report from a previous version of Crystal Reports that includes a graph, the graph formatting you have specified may not translate with the rest of the report. Crystal Reports.NET is missing the Chart Analyzer from the retail version of Crystal Reports, which allows you to use advanced formatting options on your graph. Crystal Reports.NET cannot understand this advanced formatting.
OLAP grids disappear from the report when it is imported into Crystal Reports.NETWhen you attempt to import a report from a previous version of Crystal Reports (Crystal Reports 8.5 or below) that utilizes an OLAP grid, the grid will be dropped when you import your report into Crystal Reports.NET. This happens because Crystal Reports.NET does not support OLAP data at the time of going to press, and there is currently no workaround available.
Geographic maps disappear from the report when it is imported into Crystal Reports.NETLike OLAP grids, Geographic mapping is not supported within Crystal Reports.NET. Any existing reports that have a map in them can be used, but the map area will appear blank if you import them into the Crystal Reports.NET designer.
Report Designer
Within the Report Designer itself, there are a number of areas that can be a problem, and sometimes make you think you have done something wrong (even when you haven't!). Like any product in its first release, there are still some issues to work out.
Error
Interpretation
The Field Explorer disappearsWhen working in the Crystal Report Designer, you can access the fields that are available for use with your report from the Field Explorer. If you accidentally close this window, you can get it back by selecting View | Other Windows | Document Outline or by pressing Ctrl-Alt-T.
Delete button does not function properly in the Field ExplorerNormally, when you highlight a formula or parameter field in the Field Explorer and click the Delete key, the field will be deleted. With Crystal Reports.NET, this behavior does not work. To delete the field, you will need to highlight it and press the Delete key twice. This behavior has been noted and should be fixed with future releases of the project.
Sort order of fields can not be setWhen working with record-level sorting in your report, there is no way to set the sort order or precedence, other than removing and adding the fields again in order.
The priority of the sort order in the Record Sort Order Control cannot be set directlyIn Crystal Reports.NET, the Record Sort Order control offers no direct method to set the priority order of two or more fields in the Sort Fields list. For example, there are no up or down buttons that allow you to change the list order in the Sort Fields list.If you need to modify the priority in which fields are sorted, manually remove the fields from the Sort Fields list and add them again in the desired order.
Database and Data-related
Error
Interpretation
Problems with string lengths in XML DataSets
When using XML DataSets as the data source for your reports, Crystal Reports.NET will treat all of the fields as if they have the maximum length, and think they contain 65,000+ characters. If you need to use the length for any of these fields, make sure you use trim in the Crystal Reports formula language prior to applying the record.
Errors using Set Location functionalityWhen using the Set Location functionality within Crystal Reports.NET, you can set an existing table location to a new location, for example, pointing a report from a test database to a production database. After you have finished setting the location of your data, the user interface within Crystal Reports will not be updated with this information. This is a known error and should be fixed in future releases.
Subreports
Error
Interpretation
Locating your subreport in Crystal Reports.NETWhen editing a subreport within Crystal Reports.NET (by right-clicking on the subreport and selecting Edit Subreport), a tab is added to the bottom of the page. Previous versions of Crystal Reports would open a tab at the top of the page.You can use these tabs to navigate between different subreports that exist within your main report.
A report with a subreport runs slowly or indefinitelyWith subreports, performance can be a problem if your subreport is processed multiple times. When you create a subreport and place it on a report, keep in mind that its position determines how many times that subreport will be run. For example, a subreport placed in the Report Header will only run once (as the Report Header itself only appears once).A subreport placed in the Details section, however, will run once for each detail record that is shown. In a large report, this can mean that a subeport runs hundreds of times over.If you are using subreports to display information in the Details section of your report, consider creating a SQL command, database view, or stored procedure to provide this information instead of using subreports to display the data.In addition, if you don't need to see the subreport immediately, then consider turning the report into an on-demand subreport, by right-clicking on the subreport, selecting Format | Subreport, and checking the appropriate option.
Exporting
Error
Interpretation
Formatting errors occur when exporting to Adobe AcrobatWhen exporting to Adobe Acrobat (.pdf) format, you may encounter a number of formatting errors, including:
Boxes drawn on your report lose their formatting
Double-line borders appears as single-lines
Cross-tab header only appears on first page
These are known errors with exporting to .pdf, and should be fixed in future versions of Crystal Reports.
Windows Forms Viewer
Error
Interpretation
Cancel button in the print dialog does not workWhen you preview your report in the Windows Forms Viewer, there is a print button that will allow you to print your report to the printer of your choice. You can print from this dialog with no problems, but the cancel button does not cancel the dialog.
Web Forms Viewer
Error
Interpretation
Cannot drill down into the group tree after using the ShowGroupTree methodIf you use the ShowGroupTree method, there is a bug in Crystal Reports.NET that will not allow you to drill down into the group tree. This issue has been tracked by Crystal Decisions and should be fixed in future releases of the product.
Improving the quality of images in the Web Forms ViewerWhen working with reports that contain graphs and other pictures in the Web Form, the default resolution is 96dpi. This resolution was picked based on a number of factors, including file sizing, and download times, but will often turn graphs and other images a bit grainy.There is a setting in the registry that can be changed to alter the magnification ratio for images. For more information on the necessary registry changes, go to the Crystal Decisions Knowledge Base and search for document number c2010317 for complete instructions.
XML Report Web Services
Error
Interpretation
Web Service ignores the record selection formulaWhen working with a report that has been published as an XML Report Web Service, the report's record selection formula cannot start with a commented line, as the Web Service will ignore the rest of the record selection formula and return all available records.The example below shows an incorrect record selection formula:
' This sets the record selection formula
{Customer.Country} = "USA"
and the correct version:
{Customer.Country} = "USA"
' This sets the record selection formula
Comments can appear anywhere after the first line, but never on the first line.
Access Denied Error MessageWhen working with Server File Reports (reports accessed through the generic report Web Service) you may encounter the error message: Request Failed with HTTP Status 401: Access Denied.To correct this error, you will need to ensure that the CrystalReportWebFormViewer directory is enabled for anonymous access in IIS. You will also need to restart the WWW Publishing Service before this change will take effect.
