Bug report - Crystal Reports - Report display error after updating to Crystal Report 13 SP 13

[Former Member]

Hi,

after the update from SAP Crystal Reports 13 Service Pack 9 to CR13 Service Pack 13 (downloaded from:

we are experiencing that the spacing of some letters in a multi line text field are off when the report is displayed in the CrystalDecisions.Windows.Forms.CrystalReportViewer. See the image below:

When the report is printed or saved as pdf, the text is displayed correctly.It seems to be an bug in the CrystalReportViewer. When we increase the zoom level, the displacement seems to be corrected. As seen below:

Are the more people with this problem, or is there someone with a fix? Or if someone can point me to the correct place in order to fill an bugreport (i've search, but i was unable to find the correct place for this)

Any help is appreciated.

With kind regards,

Edwin

[former_member11696 · Accepted solution]

Hi Edwin,

Did you use the exe to install into VS or did you simply add the MSI?

Is it all reports or just this one?

Try a different default printer or select a different one in the Page Setup option. If using No Printer then it is likely an issue with your display driver and possibly the font being used.

If you want to attach your report with saved data to this post I can have a closer look at it?

Use Advance Editor and rename your rpt file to *.txt.

Don

[Former Member · Accepted solution]

Hi Don, thank you for the swift reply.

The error occurs using both the executable (development pc) as the with the MSI installation (on our test server). And happens only in the attached report.

Changing the default printer to another printer did  not resolve the issue. And I doubt that this is an font issue as other text fields in the same report, using the same font, are displayed correctly.

The “character shift” only occurs on multiline text fields. For example text field Description12 in the attached report.

With kind regards,

Edwin

Report.rpt.txt.zip

[former_member11696 · Accepted solution]

Thank Edwin,

Report has no data though so not much good to me.

Can you attach a sample XML file with the schema within so I can refresh the report?

Or even better is you save the report with data or export to RPT format and attach that report. This way I can see if it's some formatting issue on your PC.

Thanks again

Don

[Former Member · Accepted solution]

Hi Don,

lets see if i can supply you with an filled report. I've attached an export from the reportviewer. It should contain data. Note that some of the fields contains random data, as you can imagine this is mainly done to keep some of the data private. Attaches is also an screenshot of the report in the reportviewer.

Hope this helps,

Edwin

HouseBL NJBEICWHZWHJ.rpt.txt.zip

[former_member11696 · Accepted solution]

Hi Edwin,

Interesting... Can you send me the xml file also. I want to see if there is anything in it that is embedded to alter the fonts...

Thanks again

Don

[former_member11696 · Accepted solution]

Hi Edwin,

Something odd in the data itself. If I export to RTF and copy that text and put it into a new report the formatting looks perfect. And notice also in Word if I set the spacing to none then it completely changes the text and is now readable...

To explain what is happening is as follows, depending on the source of the characters depends on what CR can do with it. So if the source Font caused the horizontal alignment to be off when CR uses it, even though you set the font in CR to Courier New and because the field is a Memo type we cannot apply the font change to the underlaying source.

And the differences can be caused by the Printer being used as well as the differences between USP10, should be using version 1.4 as well as GDI ( CR Designer uses it ) and GDIPlus ( .NET uses it ) Which is why it looks normal in CRD but wrong in CR WinForm Viewer...

So have a look at the XML source data and see if there is a way to set the font and other properties to something simple.

Bottom line is we cannot do anything to make this look as it does in CRD. You need to clean up the source.

Make sure the font being used in the XML does exist and is not some Custom font or some unique non-standard font.

Don

[Former Member · Accepted solution]

Hi Don,

I find it strange to believe that the error occurs because of an error in the data. The report is filled from a database varchar field. The text does not contains any ‘special’ characters. So I’m quite sure that this is not the problem. The problem started when we updated to SP13 of CR, when I use the SP9 version, everything is ok.

Furthermore, when I load the same report (same instance of the report) in a WPF ReportViewer SP 13 control (CrystalReportsViewer from clr-namespace:SAPBusinessObjects.WPF.Viewer;assembly=SAPBusinessObjects.WPF.Viewer), the report is displayed correctly. See the attached image for the difference, left side is WPF, right side Windows Forms. Therefor I still believe that there is an issue with the ReportViewer for Windows Forms, as both the Export (pdf) and the WPF ReportViewer are still able to show the correct result. I’m aware that the technology used by the WPF and Windows Forms Viewer are most likely not the same, but from an ‘end user’ point of view should not justify the difference. In my option, the result should be the same on all platforms and/or export options that are available to the developer.

But in the end, this reporting application is nothing more than a ReportViewer on a Windows Form which is called from the main application. So changing this UI to WPF is not such a big deal for us. I’m going to discuss here internally if we are going to keep using the SP9 version of CR13, or if we are moving the application to SP13, and use WPF for this UI.

Anyway, thank you for the help,

kind regards,

Edwin

[former_member11696 · Accepted solution]

Actually it does support my info. WPF viewer uses DirectX to render the report:

Windows Presentation Foundation - Wikipedia, the free encyclopedia

I suggest not using the WPF viewer and fix your data source. WPF is new to CR and has issues....

But it is up to you...

Don