Reports that use shared variables in formulas will produce differences in

data between Crystal Reports 2008 (designer) and the Crystal Reports Viewer

2008 (viewer).

The differences include:

the subreport is completely finished formatting. In the designer, the date

is updated at every page break.

of where you are drilling down. In the designer drill down views start with

an empty formula state

the first subreport is fully formatted. In the designer this is only true if the

subreports are not broken by a page break

evaluated. In the designer they are not evaluated if the subreport is in a

hidden or suppressed section and the subreport is linked to the main

report. The designer behavior is inconsistent with the behavior for other

objects with side effects.

In Crystal Reports Viewer 2008, formula side-effects do not propagate beyond

the current cell in a crosstab. In Crystal Reports 2008 side-effects are

propagated, but the behavior is not deterministic as it depends on the order

that pages are viewed.

Reports that depend on Print Date, Print Time, or related formulas (such as

Last60Days) as part of their record selection formula and do not have the

PrintDate and Time locked, will display a smaller set of data.

The viewer uses the last saved print date in the report. The smaller data set

occurs only if the data date is different from the last print date.

Crystal Reports Viewer 2008 Release Notes

Group name fields are consistent in Crystal Reports Viewer no matter whether

they are in the Group Header or Group Footer section or in the Group Tree.

Crystal Reports might have different values in the Group Footer.

Reports that use original-order grouping may display the records in a different

order when opened in the viewer.

This behavior occurs if the report data needs to be changed based on external

information (like date or time).

In general, sorting may be slightly different because the Crystal Reports

designer uses a word-based sort, but the viewer uses a Unicode sort. Certain

characters, such as hyphens and apostrophes sort differently in the viewer.

For reports that use Hierarchical grouping, and have a Group Selection

formula that filters out all records, the number that appears in the Group

Header or Group Footer may be different.

The issues that can cause a report to have different data will often also cause

the reports to have a different layout.

Instead of displaying the objects that are listed in the following table, the

viewer replaces the object with a text object that is the same size and contains

the text "<object> not supported". Because this object is displayed in the

size it was in the design view of Crystal Reports, formatting differences might

occur.

Crystal Reports Viewer 2008 Release Notes

A placeholder is displayed and, similarly, the

Map placeholder is used for exporting and printing.

A placeholder is displayed and, similarly, the

placeholder is used for exporting and printing.

OLAP Grid / OLAP

Chart

In general, subreports with saved data display correctly.

There are, however, some exceptions:

conditionally suppressed sections will not display

if they do not have saved data.

formula state for the link might have formatting

differences.

rendering, exporting, and printing are not otherwise

affected.

Subreports

The object is not supported for exporting to PDF

format. Rendering, exporting, and printing might be

affected.

Right-to-left (RTL)

languages

The object is not supported for exporting to PDF

format. Rendering, exporting, and printing might be

affected.

Thai ligatures

When exporting to RTF, images are exported one

Images to a line.

Crystal Reports Viewer 2008 Release Notes

font in Crystal Reports. This difference leads to line-height differences.

As a result, reports where you have a multi-line text object next to which

you have placed other objects to align them vertically, may not appear

correctly.

space, which means that some reports are paginated differently.

substitutes a font from the machine (if no matching font can be found, the

viewer defaults to Arial). This action may lead to text measurements that

are not the same.

Charts may appear differently in the viewer. However, the general layout

and overall meaning of the chart will not change. There are a few specific

differences that you might notice:

chart. This sometimes leads to differences in label settings and frame

size so that labels won't overlap.

Crystal Reports allocates space to an empty subreport, even though you

have selected the 'Suppress Blank Subreport' option. This behavior causes

sections containing blank sub-reports to grow larger. The behavior does not

occur in the Crystal Reports Viewer.

Currency symbol may appear differently in position and appearance in Crystal

Reports for Eclipse and Crystal Reports Viewer compared to Crystal Reports

2008.

For example, when viewing reports containing currencies in Russian locale,

the Russian currency symbol is py6#### instead of ####p.

Crystal Reports Viewer 2008 Release Notes

The following table summarizes the major printing limitations that you might

encounter in the Crystal Reports Viewer.

Use local printer

setting

8.5 x 11 rendered

using

no printer setting

8.5 x 11 rendered

using

no printer setting

N N

Use local printer

setting

Use the default

printer

settings of the

report consumer

machine

Use the default

printer

settings of the

report consumer

machine

N Y

Use local printer

setting

Use custom

page size; create

best match

between new

printer settings

and original

printer

Custom page

size with local

printer configuration

Y Y

If you open a report in which the paper size selected by the report designer

is not available, the Crystal Reports Viewer will display the report in its original

paper size. If you print the report from the viewer, the output is reduced to

fit to the default paper size.