Hi,
when I try to print a grid, sometimes this message appears:
In case the message appears, e.g. only 7 of 9 pages are printed.
When I change the Header height from e.g. 50 to 40 or 60, or decrease the size of the font, it sometimes works normally again. After a few days, when the data of the grid changed, the error appears again.
I can't catch or hide this messagebox, no exception appears.
I set these attributes of ultraGridPrintDocument:
This is the grid I want to print:
This is the printed grid, where the last 2 pages are not generated:
The header text is the same on every page.
Please help me.
Best regards
I got the same problem when trying to print this grid.
I'm printing several different reports and some work, some don't. There seems to be no rule regarding the length of the report or some things like that. Sometimes i get the error when printing in landcape-mode and changing the mode to portrait makes the error disappear. Sometimes the error pops up in portrait-mode AND in landscape mode.I even tried to print the grid without any header, still the error keeps popping up.
Changing the header height or the font size helps to print one report. But then another one, which was printable before the change shows the error.I don't know what to change anymore. Any help would be highly appreciated.
This sounds like it's pretty clearly a bug. But without being able to duplicate the issue, there's really no way I can track down what's causing it.
Can you provide a sample project that we can run to duplicate the error?
Mike,
Opened case CAS-41462-BK5J6A this has a project attached that recreates the problem.
ThanksRon
Thanks Ron,for open a ticket and for setup a sample project.
do have any reply from the "support" guys?
Good luck.
Hi Davide,
Last I have heard is that it was being assigned to a developer.
Ron
This has been plaguing us intermittently for about a year now. Any word?
The issue reported here was fixed back in March, so you probably just need to get the latest service release.
If you have the latest service release and you are still having a problem, then the issue you are experiencing must be different than the one discussed here.