Documente Academic
Documente Profesional
Documente Cultură
Release Notes
Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.
chapter
1 Crystal Reports for Visual Studio 2005
About these notes
chapter
2 Crystal Reports
Registration
Registration
• You must have administrator access to enter or change the registration
key.
Crystal Services
• After expanding the Server Explorer, you may see the following error
message: “Enterprise connectivity has not been detected on this
machine. Please install the BusinessObjects Enterprise .NET SDK from
Crystal Reports Server or BusinessObjects Enterprise and try again."
Workaround: Install the BusinessObjects Enterprise XI Release 2 .NET
SDK and Crystal Reports XI Release 2.
Migration
• Parameter prompting is a new feature. After you have migrated your
application, when you refresh a report, the application prompts for the
value of the parameter, instead of fetching the value of the parameter in
the code. To turn off parameter prompting, set
ReuseReportParametersOnRefresh to false on the CrystalReportVeiwer
control.
• To set the viewer selection formula to display all records in a report, use
the empty string instead of the null string. The null string fails to override
the original report-selection formula. The empty string is represented as
"" or String.Empty. The null string is represented as null in C# or Nothing
in Visual Basic.
• References to the CrystalDecisions.ReportSource,
CrystalDecisions.Shared, and CrystalDecisions.Windows.Forms
assemblies are lost when a Windows Project from Crystal Reports 9 or
Crystal Reports 10 is migrated to Crystal Reports for Visual Studio 2005.
After migration, add the references manually, or upgrade to Crystal
Reports XI Release 2. Note that, when migrating Crystal Reports 9 and
Crystal Reports 10 projects to Visual Studio 2005, you may lose some of
the functionality that you had from the full version.
Formatting reports
• When you add a Special Field to a report, although the Special Field has
been successfully added, a checkmark icon beside the field fails to
appear in the Field Explorer.
• After a field is re-mapped in the report designer, the Field Explorer fails to
display the new field name. The field name in the report is correctly
modified; however, the name in the Field Explorer does not update
correctly.
Web sites
• If you run a project with a version 6 or earlier Crystal report that is based
on a query with saved data, an error message may appear. The cause of
the problem is that the refresh feature for query reports is not supported
in Crystal Reports version 7 and later.
• When you open a report that was created in Crystal Reports version 6 or
earlier, the chart template is automatically removed from the report.
• Reports created in Crystal Reports version 10 or earlier that contain
textured charts may contain X’s rather than the correct texture.
• When you view a report that has tables with the data source set to
IDataReader for each one, and many of the tables are linked together,
you may see the following error message: "Invalid database argument."
Calls made to SetDataSource() from an IDataReader are supported only
for reports that contain one table.
Workaround: To use an IDataReader with multiple tables, create a
report with one command table that selects the necessary fields.
• If the DataSource tag of a CrystalReportSource tag is bound to an object
that has more than two dependencies, the viewer will show incorrectly
filtered data when a page is first loaded.
Workaround: In the Page_Init() or OnInit() method of your application,
call control.DataBind(), where “control” is the control to which your
DataSource is bound.
• When you change the SelectionFormula property of a webform viewer at
run time, a new set of data isn't retrieved until you click Refresh.
Workaround: To refresh the report and display the report using the new
selection formula, call ReportDocument.Refresh().
• SetDataSource does not support strongly typed datasets with NULL
values that have been cast to an IEnumerable object.
Workaround: Convert the IEnumerable into a DataTable and use
SetDataSource(DataTable).
• When parameter values are set with tags, and then a parameter that
doesn't exist in the report is entered as the first parameter value, an error
message may appear at run time.
Workaround: Only add parameters that exist in the report.
• Verifying a database through code that uses the
ReportDocument.VerifyDatabase() method may throw an exception. This
problem happens when you use a strongly typed report class that needs
no database logon, such as Access or ADO.NET.
Workaround: Call the SetDatabaseLogon() method before you call the
VerifyDatabase() method. For example:
ReportDocument rpt = new ReportDocument();
rpt = new StrongReportClass();
rpt.SetDatabaseLogon("","");
rpt.VerifyDatabase();
• When you use the New Project dialog box to create a Crystal Reports
Web Application, some report formatting may display incorrectly. The
cause of the problem is a missing link from the default.aspx page of the
Crystal Template Web application to the CrystalReportWebFormViewer3/
css/default.css file. The absence of this link causes formatting problems
for certain report objects that use customized formats, such as the CSS
style Class Name.
Workaround: To ensure that report objects with customized formats will
display properly, add the following link to the default.aspx page: <link
href="/aspnet_client/System_Web/2_0_50727/
CrystalReportWebFormViewer3/css/default.css" rel="stylesheet"
type="text/css" />
• When you view the parameter list of a CrystalReportSource control in the
Crystal Reports Parameter Collection Editor, all the parameters in the
main report and subreports are displayed. The radio buttons in the
Crystal Reports Parameter Collection Editor show whether the currently
selected parameter is a main report or a subreport parameter. The
buttons do not filter the parameter list.
• The webform CrystalReportViewer fails to let you set the
SelectionFormula property at run time when you use the viewer's View
list.
Workaround: Clear the View list, by setting the ReportSource of the
viewer again after you set the SelectionFormula property.
• Object borders will not display when viewing a Crystal report with the
CrystalReportViewer in an XHTML 1.1 document.
</xsd:complexType>
• For XML fields that contain simple content only, a report can only display
the value in XML format.
• When performing “group by” on a server based on XML instance fields,
the following MS SQL Server error message may appear: "XML methods
are not allowed group by clause."
Workaround: Disable “perform grouping on server” for the report.
• For XML fields that contain only complex-type content or contain
attributes, a report will fail to display the hierarchical structure of the field.
• XML instances of certain XML string types are unable to be displayed in
the Field Explorer. Those XML string types are as follows:
• token
• language
• NMTOKEN
• Name
• ID
• NCName
• anyURI
• After you change the name of a child field for an XML field in a report, and
then view the report, an error message may be displayed. The cause of
the problem is that the verify function fails to be called, even when the
report option verify on first refresh is enabled.
Workaround: Explicitly call the verify method.
• Fields cannot be remapped to a sub-component of an XML table. When
you map fields to an XML table, only the first level of columns for the
target table are displayed.
• When you create a SQL expression field based on an XML instance field
in the SQL expression editor, the following error message may appear:
"Invalid object name."
• When you view a link report based on XML tables where the XML
instance fields have same instance name, the following error message
may appear: "The correlation name is defined multiple times in FROM
Clause."
• A report based on an XML table will fail to load if the first relational field in
the XML table has been deleted.
Workaround: Add the field back to the database table.
appendix
A Documentation and information services
Documentation
You can find answers to your questions on how to install, configure, deploy,
and use Business Objects products from the documentation.
Address Content
Business Objects product Information about the full range of
information Business Objects products.
http://www.businessobjects.com
Product documentation Business Objects product
http://support.businessobjects.com/ documentation, including the
documentation Business Objects Documentation
Roadmap.
Business Objects Documentation Send us feedback or questions
mailbox about documentation.
documentation@businessobjects.com
Online Customer Support Information on Customer Support
http://support.businessobjects.com/ programs, as well as links to
technical articles, downloads, and
online forums.
Business Objects Consulting Information on how Business
Services Objects can help maximize your
http://www.businessobjects.com/ business intelligence investment.
services/consulting/
Business Objects Education Information on Business Objects
Services training options and modules.
http://www.businessobjects.com/
services/training