Friday, March 23, 2012

Formatting Problems Cont. . . MS PLEASE ANSWER

This is a variation of a post from earlier. I have noticed significant
differences between the on screen vs printed/exported versions of every
report I have done. If a report looks good on the screen, things are so out
of place on the print out/pdf versions that I would never give them to a
customer, and vice versa. Is there something I am doing wrong? Here are
some specific problems:
1) One report has a subreport with nothing more that a single table, it is
displayed at the center at the bottom of one report. When the report is
printed, the subreport is moved so far to the right that it prints on a whole
new page.
2) In that same report, I cannot leave blank space at the bottom after the
subreport, regardless of whether I leave a some space in the report,
subreport, or both.
3) Blanks in the returned data from a stored procedure are ignored
sporadically in my report matrices.
4) All reports extend an inch or so the the right for no reason, moving
everying out of center, and disconnection horizontal lines from their right
hand borders.
If you are reading this post and have not yet chosen whether to use MS
Reporting Services or Crystal, unless someone has given an answer explaining
how to fix these issues, I strongly suggest you use crystal. It will be
cheaper to pay their licensing fees than to deal with the development time of
RS. As far as I can tell, the 2000 version is a miserable excuse for a
release. It should still be a beta.I suggest you open an incident with support. Or, if you have MSDN you can
use managed newsgroups (which is posting here using a registered alias so MS
knows to monitor the post). Just posting here is not guaranteed a response
from MS. It is peer supported. It very well could be that there are work
arounds to your issues. Or ways to design that there is not a problem. RS is
not Crystal and Crystal is not RS. Some things RS does very well, others not
so well. It is a output independent development environment and things can
vary based on the capabilities of the output.
Given how you did not even try to first find out whether there was a
solution before being insulting I'll let others jump in if they want to.
That is the problem with peer support. If you are nasty your peers won't
want to help. I sure don't (and if you hang here at all you will see I help
a whole lot of people).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Evan" <Evan@.discussions.microsoft.com> wrote in message
news:4F087219-EE00-46DA-AEA5-7A073C243FCE@.microsoft.com...
> This is a variation of a post from earlier. I have noticed significant
> differences between the on screen vs printed/exported versions of every
> report I have done. If a report looks good on the screen, things are so
out
> of place on the print out/pdf versions that I would never give them to a
> customer, and vice versa. Is there something I am doing wrong? Here are
> some specific problems:
> 1) One report has a subreport with nothing more that a single table, it is
> displayed at the center at the bottom of one report. When the report is
> printed, the subreport is moved so far to the right that it prints on a
whole
> new page.
> 2) In that same report, I cannot leave blank space at the bottom after
the
> subreport, regardless of whether I leave a some space in the report,
> subreport, or both.
> 3) Blanks in the returned data from a stored procedure are ignored
> sporadically in my report matrices.
> 4) All reports extend an inch or so the the right for no reason, moving
> everying out of center, and disconnection horizontal lines from their
right
> hand borders.
> If you are reading this post and have not yet chosen whether to use MS
> Reporting Services or Crystal, unless someone has given an answer
explaining
> how to fix these issues, I strongly suggest you use crystal. It will be
> cheaper to pay their licensing fees than to deal with the development time
of
> RS. As far as I can tell, the 2000 version is a miserable excuse for a
> release. It should still be a beta.

No comments:

Post a Comment