Hi, I updated CR 13 to 13 SP4 (VS2010 ASP.NET)
I'm having a lot of reports that are working properly. Now (SP4), when I open a report on a CR viewer the report isn’t rendering correctly but when I print the report everything is correct.
If the compatibility mode is ON in IE9 the rendering is better, not OK, but I can’t use it as other funcionalities of my product are having problems.I have attached the screen shot.
What can I do to solve it?
Now (SP4), when I open a report on a CR viewer the report isn’t rendering correctly but when I print the report everything is correct.
Does this mean that before SP4, you did not have the issue?
See if setting the "No Printer" option helps.
Follow us on Twitter
Got Enhancement ideas? Try the SAP Idea Place
Re. SP4 roll back. This was just an idea and I understand the need for SP4 may be related to a fix that is in SP4. I will test this to see if I can reproduce the issue with our reports. If I can, then I will escalate the issue for a fix, ETA; if I can get it into SP5 then we're looking at beginning of October. If not, then we're looking at SP6 - probably January 2013.
If I cannot reproduce the issue, I may need your report with saved data to test with.
Have a great weekend,
I've been able to reproduce the issue - with IE8 as well as IE9 and I will be creating a technical escalation for this. The issue, as far as I am concerned, is significant and I'd expect it to be resolved in Service Pack 5, ETA; mid October(?) - no promises at this time. I'll update this thread as soon as I have a TE number.
Please check back mid September for status update.
Good morning Ludek,
I’d prefer a Fix to solve the issue, but I perfectly understand it isn’t always possible.
We shall try to placate the customer's complaints regarding the error until October.
Many thanks for your help detecting and trying to solve it.
I don’t know how to proceed with the ID that you have sent me: TE5000433703 and (DAPT01651895)
scenario: visual studio 2010 and CR for VS2010 13.0.1, in the image on the left the report inside the crystalreportviewer and on the right in a desktop application.
As you can see the report inside the crystalreportviewer has visualization problem, it can be the same issue reported by Jordi?
Depends which issue as we kinda mixed in here two of em:
1) The original issue of detail lines over printing headers posted as the original entry on July 13
2) Placing formula into text box so that the contents do not spill beyond a set length
(1) will be fixed in SP 5, now scheduled for December 2012
(2) is not considered to be a "fixable" issue, so no escalation
And to answer your question re following the tracking number; that's a trick and a half for me using our internal systems , so nothing public... but once these SPs get released I do create wikis that document each fix in the SP.