Major Changes in Release 7
 

i-net Crystal-Clear runtime

i-net Crystal-Clear - Java Viewer

i-net DesignerXML

i-net Crystal-Clear Setup

The formula functions BytesFromFile and TextFromFile now interpret relative paths as being relative to the report file itself.

Excel export: The report title is now used as the sheet name if it is specified in the rpt file.

i-net Crystal-Clear can be forced to use a certain Database class for communication with a database by specifying a Database class name for a Data Source Configuration.

Font Path: It is now possible to specify multiple paths comma separated in the property Font Path (supported in version 7.9.03).

Cascading prompts supported for multi-value prompts, also (in version 7.9.11).

Faster string comparison when rendering with multiple threads (in version 7.9.15).

Function TextFromFile supports URL's with protocols other than “file”, e.g. “http” (in version 7.9.17).

Postscript Export: Compression of monochrome blob images supported (in version 7.9.20).

HTML Parameter Request dialog translated depending on the client locale (in version 7.9.26).

java.awt.HeadlessException occurred if the Listener was started headless with parameter: -Djava.awt.headless=true.

PS Export: JBarcodeBean was displayed only once per report page.

Excel export:

Text export: Some labels could be missing in mailing label or multi-column reports if one or more sections were suppressed.

RTF export: Bug 'invalid Border around a picture' could occur if a border was used for a text field in the report.

RDC API:

Data Source Configuration Manager:

A bug that overriding Database classes did not work correctly has been fixed in version 7.9.01.

Exceptions with cascaded if-then-else statements in formulas with basic syntax has occurred (fixed in version 7.9.02).

Formulas in Crystal Reports 9 (or higher) reports had sometimes the wrong return type (e.g. number instead of string)
if they are not used as formula field in the report (fixed in version 7.9.03).

The last elseif block in basic syntax formulas has been ignored if it was not followed by an else block (fixed in version 7.9.03).

Barcode font was wrongly interpreted as a symbolic font, leading to i-net Crystal-Clear using the wrong character range (fixed in version 7.9.05).

Using Oracle DataIntegrator JDBC driver for XML the report execution could have failed because of invalid SQL (fixed in version 7.9.06).

Chart: Duplicated values on the data axis have occurred if the automatic calculated step width was smaller than the user defined format (fixed in version 7.9.06).

Function time change a PM time to an AM time (fixed in version 7.9.07).

PS export: Symbolic fonts like Windings were displayed as square boxes in the exported postscript files, also if postscript level 3 with font embedding was used (fixed in version 7.9.07).

Reports based on JDBC drivers which don't support joins in WHERE and FROM clause did not return the correct data as e.g. joins between tables were not regarded. (fixed in 7.9.08)

Section property “New Page After” were ignored for suppressed sections (fixed in 7.9.08).

Endless Loop occurred if section properties “Print At Bottom of Page” and “Suppress Blank Section” has been used in combination with sections spanning multiple pages (fixed in version 7.9.09).

Excel Export: Cells without content does not have a background color even when the background color was set in report design (fixed in version 7.9.09).

Since Java 1.6.0_02 it can occur that fields with Text Interpretation “HTML (advanced)” will be displayed incorrectly. Some HTML parts (for example text) can be truncated on the start of the second or following pages. (fixed in version 7.9.10).

Postscript Export: Printer has run out of memory if the postscript document contains a lot of dynamic images from a database (fixed in version 7.9.10).

HTML Export: Leading white spaces in rows with justified alignment were not displayed in exported file (fixed in version 7.9.11).

PDF export: Problem while printing exported PDF files via IPP occurred (fixed in version 7.9.12).

Text export: “Page N of M” field was incorrectly positioned if there was a field with Asian characters on the left side of the field (fixed in version 7.9.12).

Number field property “Show Zero Value as” has not worked correctly for number value ”-0.0” (fixed in version 7.9.13).

PDF export: Underline too long for bold Chinese text (fixed in version 7.9.13).

Data export: Order of columns could be wrong if suppressed elements are included
(fixed in version 7.9.14).

Excel export:

HTML export: Width of fields with “Advanced HTML” text interpretation sometimes incorrect (fixed in version 7.9.14).

When using a language resource bundle for labels with mixed Field parts and Text parts, there could be an internal NullPointerException leading to the label not being translated (fixed in version 7.9.15).

A sporadic error “java.lang.ArrayIndexOutOfBoundsException: 1986618432” occurred during long-running HTML exports was fixed (fixed in version 7.9.16).

Strings with two slashes, such as URLs, were parsed incorrectly in formulas, leading to the formula being truncated at the slashes (fixed in version 7.9.16).

It has occurred that database connections that has been set using API were not closed after parameter fields has been requested from the Java viewer (fixed in version 7.9.17).

PDF export: Underscore of bold fonts sometimes longer than text (fixed in version 7.9.17).

Exception occurred while using number format property formulas in cross-tab cells, which contains the keyword “currentfieldvalue” (fixed in version 7.9.17).

Sometimes sub-report was empty if sub-report link field was null (fixed in version 7.9.17).

Formula was truncated although “Can Grow” was activated (fixed in version 7.9.17).

Excel export: If the height of a text contained in a text element was less than the height of the field itself, the lower boundary of the cell in the Excel sheet was doubled (fixed in version 7.9.17).

Cross-Tab:

Some JavaBeans were not displayed in exported PDF and RTF files (fixed in version 7.9.18).

“Can Grow” fields with trailing spaces would show up with an unwanted line break
(fixed in version 7.9.19).

PDF export: Representation of blank content was wrong. Page in PDF file was blank if total page element was empty (fixed in version 7.9.19).

Excel export: Position of “sub-report on demand” label without borders and background color was incorrect (fixed in version 7.9.20).

PDF export: Box spanning multiple sections was not displayed correctly  (fixed in version 7.9.22).

Sometimes a section disappeared if the Page Footer section was suppressed depending on a formula (fixed in version 7.9.22).

Excel export: Line was missing sometimes in created .XLS file (fixed in version 7.9.23).

TXT export: Chinese data were shifted sometimes if the data contains the Chinese character “VIII” (fixed in version 7.9.23).

ODBC driver for Excel mark all sheets as SYSTEM TABLE. Therefore no objects were displayed in the Visual Database Wizard (fixed in version 7.9.23).

TXT export: Chinese data were shifted sometimes (fixed in version 7.9.24).

Wrong result of DateDiff function with a DayOfWeek offset occurred if the difference was a multiple of seven days (fixed in version 7.9.24).

RTF export: The value of the font leading for the font Arial Unicode MS was incorrect. Therefore some elements with enabled “Can Grow” were truncated at the bottom (fixed in version 7.9.25).

Non-ASCII characters in parameter field names are not displayed correctly in the HTML Parameter Request dialog. (in version 7.9.27).

XLS export: Values with data type Byte was not displayed in exported XLS file (fixed in version 7.9.29).

SwingViewerContext now has a constructor which accepts a SwingReportViewer parameter. This enables the ViewerContext to create a modal dialog with the SwingReportViewer as its parent.

Print Dialog: With the properties button on the General tab it is now possible to open the native print dialog if the Java VM does not provide a properties dialog for the used printer.

Time parameter fields now have a more user-friendly entry box in the viewer prompt dialog.

SwingReportViewer.setLoggingStream was added as a static method so that the initialization of the Viewer no longer has to be logged to the System.out stream.

The viewer now has a context menu available. This menu contains the items “Refresh”, “Export”, and (if the clipboard is enabled and text is selected) “Copy” and “Clear Selection” - copying to the clipboard used to only be accessible through the keyboard shortcut “Ctrl+C”.

Paper format “A2” supported (supported in version 7.9.04).

Export dialog: Report Title is used as file name for the exported file. If Report Title is not specified then the file name of the rpt file will be used (supported in version 7.9.14).

Russian translation of the GUI added (in version 7.9.27).

If copying to the clipboard is not enabled for a report, the text selection option was still enabled but had no effect.

The viewer could show a NullPointerException if one of the default values for one of the prompts was explicitly set as null.

If more than one default value had the same value, the identical default values were ignored.

The group tree always used a default L&F instead of the L&F set by the application.

Manually calling the method SwingReportViewer.setCurrentReportView() did not have an effect on the GUI of the viewer.

When showing a report stored in a JRA, it could happen that the total number of pages was never shown in the viewer.

The interface ReportViewChangeListener was obfuscated and was unavailable to API users.

Exceptions occurred if multi-LAF was used (fixed in 7.9.01).

If Java VM 5.x was used for Java viewer, print dialog was slow during first start (fixed in 7.9.04).

Exception “Wrong packet size” has occurred sometimes during export (fixed in 7.9.04).

SwingToolBar.isButtonsVisible() and SwingToolBar.setButtonsVisible() did have no effect for buttons ToolBar.BUTTON_JRA_SAVE and ToolBar.BUTTON_JRA_LOAD (fixed in 7.9.05).

NullPointerException occurred if the viewer was closed while the field “Current Page” in the toolbar had the focus (fixed in 7.9.05).

Toolbar Buttons were displayed “compressed” if Java viewer was executed with Java 5 (fixed in 7.9.05).

Error “Wrong packet size received” occurred or exported file has been truncated if a proxy server used gzip content encoding (fixed in 7.9.06).

There was an issue with cascading prompts in the Java Viewer which could cause prompt values to not be fetched after choosing the parent prompt's value (fixed in 7.9.10).

Landscape reports were not printed correctly if “2 Pages per Sheet” was set in the print dialog of the Java report viewer (fixed in 7.9.21).

Added Constructor

Added Method

Parameter Field Properties dialog:
It is now possible to select more than one default value in the default value table and delete them at once.

Parameter Field Properties dialog:

Formula Editor:

SQL Editor:

Various minor GUI issues were fixed for the Report Wizard.

When a Record Selection Formula was only a comment with no return value, an error was shown.

Under rare circumstances, the Report Wizard could not be closed by pressing OK.

The font list has been made more user friendly - it is now possible to enter a font name, and the font name will be auto-completed, also the font list will jump to the selection.

Formula Editor:

In some cases, the Report Wizard would incorrectly show an error when using table sources from more than one connection (fixed in 7.9.06).

Under certain circumstances it was possible that sub report links were lost when opening and saving a report with i-net DesignerXML (fixed in 7.9.10).

The methods DesignerDataModel.AddedElement() and DesignerDataModel.isAddElementAllowed() has not worked correctly (fixed in 7.9.14).
The method addedElement of the DesignerDataModel interface will now be invoked whenever an element will be added to the report, also if an element will be added in consequence of another operation (e.g. sub-elements of a cross-tab).

With certain Look and Feels such as the Vista L&F, it was possible to generate an internal NullPointerException in the Designer prompt dialog, leading to GUI issues (fixed in version 7.9.18).

Blank screen occurred in Chart Properties dialog if Designer runs with Java 6 Update 11 or higher (fixed in 7.9.28).

Error box occurred on Windows 7 during start of i-net DesignerXML if node “com\inet\designer\classes” does not exist in Java preferences (fixed in 7.9.31).

Version 4.5 of the PHP/Java Bridge added for PHP 5.2.

WebLogic Servlet: Location of the file web-app_2_3.dtd in the web.xml was wrong.