TrueType fonts which were incorrectly initialized were displayed with a height of 0.
Property “Print At Bottom of Page” did not work correctly for areas. Each section of an area was displayed at the bottom of a separate page.
There was a rarely occurring problem that old reports with summary fields were not able to be read.
Endless loop occurred if Underlay Following Section was enabled for a large section.
StackOverflowError occurred if nested if-then-else statements used in formulas.
There was a problem reading a Crystal Reports template with ReportReader, the message was “Object reference not set to an instance of an object”.
Exception “Invalid render state” occurred if a “new page after” section was encountered before a section had been displayed.
Lines and boxes that are continued on the next page, started under the page header. Now, they start under the repeated group header.
Lines with “Move to Bottom of Section when Printing” enabled were not displayed on the next page if the section spanned multiple pages.
Element borders were drawn into adjacent sections if the element was on the edge of the section.
The multi-column layout of a report was incorrect if it was used together with the section property “Underlay Following Sections”.
The set line width of boxes was used for positioning the boxes even when line style was set to NO_LINE.
Formulas:
The population standard deviation summary function now returns an empty value until a valid value has been read.
Because of a bug it was not possible to use string range promts in formulas.
Problems with user-defined functions occurred if Java primitive types were used as method parameters.
The formula function 'isnull' was executable on the database if it's parameter was a boolean field.
It was not possible to overwrite a variable, that was created with StoreNumberVar in the main report, with StoreNumberVar in the subreport.
Excel Export:
Cross-Tabs were incorrectly displayed when exporting the report to Excel format. The first column was not exported.
Thousand separator not displayed if procent format was used.
The position of the '%' -symbol has not been set, if the log level was lesser than WARNING.
Security issue: Using a modified report
URL, it was possible to download files from the i-net Crystal-Clear web context, if the file crystal.war was unpacked.
Report Reader: Mailing label and multi column reports were not read properly by the .NET-based Report Reader.
A subreport in the page footer was not displayed if the first subreport section was higher than the subreport itself.
Error with database column of type CHAR occurred if it contains empty strings.
If muliple directories has been specified in “Font Path” property and occurred an error during reading fonts from one directory, then the other directory was not read.
Names of embedded fonts in the font path has been searched only case sensitive.
NullPointerException occurred if user defined string collation for grouping and sorting was used with an empty locale.
IllegalDatePeriodException occurred if time field was used as column or row in a crosstab.
Changing the alias of a table source led to problems when the report had an SQLField as an element in the report.
An endless loop in the scheduler occurred with large scheduler jobs, if hard disk cache or database cache was used.
ReportReader: The formatting of field parts in text labels was not correctly read from Crystal Reports templates.
Text export:
Data export:
Set and reset reference of a summary field by group with TopN was faulty.
