I'm having a problem with a report i recently built. I use a table
with three colums and one issue I have is there is a lot of white
space left all over the report because a table group will not span
onto the next column.
With the exception of one group that is larger than 1 entire column.
That one actually fills up one column and then starts agian at the top
of the next column.
Has any one else ran into this?
Also if you know how to potentially fix this let me know.
Thanks,
GregHave you tried Merging several cells to span the columns?
"Greg" <greg.cheadle@.gmail.com> wrote in message
news:1183647511.082603.121240@.q69g2000hsb.googlegroups.com...
> I'm having a problem with a report i recently built. I use a table
> with three colums and one issue I have is there is a lot of white
> space left all over the report because a table group will not span
> onto the next column.
> With the exception of one group that is larger than 1 entire column.
> That one actually fills up one column and then starts agian at the top
> of the next column.
> Has any one else ran into this?
> Also if you know how to potentially fix this let me know.
> Thanks,
> Greg
>
Showing posts with label paging. Show all posts
Showing posts with label paging. Show all posts
Wednesday, March 28, 2012
Report Paging
This is a multi-part message in MIME format.
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
How do I define the number of lines per page in Report Designer? I have = defined the report as 11" x 8.5" landscape but when I preview or print, = I am getting alternate correctly numbered pages consisting just a report = header & report footer. I'm assuming that it is related to an issue = with rows per page, but am unable to find the definition to give that a = try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
How do I define the = number of lines per page in Report Designer? I have defined the report as = 11=94 x 8.5=94 landscape but when I preview or print, I am getting alternate correctly = numbered pages consisting just a report header & report footer. I=92m = assuming that it is related to an issue with rows per page, but am unable to find = the definition to give that a try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040--On Jun 20, 2:31 pm, "Joe" <hortoris...@.gmail.dot.com> wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try.
What is the width of the report body? If the body is wider than page
then you will get these extra pages. It doesn't matter if there is
nothing to display, it will still think your report needs to be that
wide.|||There's a good explanation of report paging in
http://blogs.msdn.com/bwelcker/archive/2005/08/19/454043.aspx.
However, even having followed the instructions on this blog, we have
problems with report paging as well. We seem to have some reports that show
fewer pages in the report viewer than when they are printed to pdf or the
printer. We even have one report, that depending on the parameters, shows as
a single page in the viewer and many pages when printing in pdf or the
printer. Are there other people having these problems as well?
"Joe" wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
How do I define the number of lines per page in Report Designer? I have = defined the report as 11" x 8.5" landscape but when I preview or print, = I am getting alternate correctly numbered pages consisting just a report = header & report footer. I'm assuming that it is related to an issue = with rows per page, but am unable to find the definition to give that a = try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
How do I define the = number of lines per page in Report Designer? I have defined the report as = 11=94 x 8.5=94 landscape but when I preview or print, I am getting alternate correctly = numbered pages consisting just a report header & report footer. I=92m = assuming that it is related to an issue with rows per page, but am unable to find = the definition to give that a try.
--=_NextPart_000_00B0_01C7B32E.8ACDD040--On Jun 20, 2:31 pm, "Joe" <hortoris...@.gmail.dot.com> wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try.
What is the width of the report body? If the body is wider than page
then you will get these extra pages. It doesn't matter if there is
nothing to display, it will still think your report needs to be that
wide.|||There's a good explanation of report paging in
http://blogs.msdn.com/bwelcker/archive/2005/08/19/454043.aspx.
However, even having followed the instructions on this blog, we have
problems with report paging as well. We seem to have some reports that show
fewer pages in the report viewer than when they are printed to pdf or the
printer. We even have one report, that depending on the parameters, shows as
a single page in the viewer and many pages when printing in pdf or the
printer. Are there other people having these problems as well?
"Joe" wrote:
> How do I define the number of lines per page in Report Designer? I have defined the report as 11" x 8.5" landscape but when I preview or print, I am getting alternate correctly numbered pages consisting just a report header & report footer. I'm assuming that it is related to an issue with rows per page, but am unable to find the definition to give that a try
Report Paging
We are converting from Crystal Reports to Reporting Services. We are
encountering what appears to be an issue with the Report Viewer. If Table
rows in the body of the report are conditionally made Hidden (depending on
parameter input), the number of pages differs between the viewer and the
printed (either printer or pdf). In fact, some reports show a single page in
the viewer, but many pages when printed or exported to pdf. If the Table rows
are always visible, the pagination is consistent between viewer and printing.
Is there any way to work around this?Hello HK,
I would like to know the following things:
1. What's the SQL server version did you use? 2000 or 2005?
2. Since this issue only occured for the conditional Hidden, it is a known
issue in SQL 2005. And the product team is researching this issue. If I get
any update, I will let you know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you for your response.
We are using sql server 2005 sp2, visual studio 2005.
It appears to be occuring only with the conditional Hidden. If I remove the
conditional Hidden, we appear to get correct pagination. I (and our many
report users) would greatly appreciate any solution to this.
"Wei Lu [MSFT]" wrote:
> Hello HK,
> I would like to know the following things:
> 1. What's the SQL server version did you use? 2000 or 2005?
> 2. Since this issue only occured for the conditional Hidden, it is a known
> issue in SQL 2005. And the product team is researching this issue. If I get
> any update, I will let you know.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello HK,
Product Team confirmed this is a known issue and will be addressed in the
next version of Reporting Services.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I'm glad to hear that - thanks for your response.
"Wei Lu [MSFT]" wrote:
> Hello HK,
> Product Team confirmed this is a known issue and will be addressed in the
> next version of Reporting Services.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
encountering what appears to be an issue with the Report Viewer. If Table
rows in the body of the report are conditionally made Hidden (depending on
parameter input), the number of pages differs between the viewer and the
printed (either printer or pdf). In fact, some reports show a single page in
the viewer, but many pages when printed or exported to pdf. If the Table rows
are always visible, the pagination is consistent between viewer and printing.
Is there any way to work around this?Hello HK,
I would like to know the following things:
1. What's the SQL server version did you use? 2000 or 2005?
2. Since this issue only occured for the conditional Hidden, it is a known
issue in SQL 2005. And the product team is researching this issue. If I get
any update, I will let you know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you for your response.
We are using sql server 2005 sp2, visual studio 2005.
It appears to be occuring only with the conditional Hidden. If I remove the
conditional Hidden, we appear to get correct pagination. I (and our many
report users) would greatly appreciate any solution to this.
"Wei Lu [MSFT]" wrote:
> Hello HK,
> I would like to know the following things:
> 1. What's the SQL server version did you use? 2000 or 2005?
> 2. Since this issue only occured for the conditional Hidden, it is a known
> issue in SQL 2005. And the product team is researching this issue. If I get
> any update, I will let you know.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello HK,
Product Team confirmed this is a known issue and will be addressed in the
next version of Reporting Services.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I'm glad to hear that - thanks for your response.
"Wei Lu [MSFT]" wrote:
> Hello HK,
> Product Team confirmed this is a known issue and will be addressed in the
> next version of Reporting Services.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
Subscribe to:
Posts (Atom)