Paging issue on conditionally set second table visibility

Hi. I am having a problem with a 2005 report that has two tables and is designed thru visual studio. The second table is set to page break before printing and also to repeater headers on new pages. It works fine just like that. However, if I place a condition on the visibilty of the table based on an input report parameter it does not page break before rendering the table. In fact it does not page break at all leaving me with an extremely long last page. The visiblity parameter does properly toggle. This is all occurring when rendering the report to the screen using the windows reportviewer. When I export to PDF it looks fine.

Any help would be great.

This is currently by design - when the visibility property is expression-based, the page break is ignored. We are considering changing this behavior in the next release.|||

Thanks for the reply Fang.

I do hope you consider chaninging it. I can understand ignoring the page break when visibility is false but I am not sure why one would want to ignore it when visibility is true. Also, the way it is now the rendered report is not consistent between the screen and PDF.

|||Thanks so much for posting your problem. We are converting from crystal to reporting services and have been experiencing this same issue and were very puzzled. This "by design feature" is making a lot of our reports look very inconsistent with pagination between the viewer and printer or pdf. Reminds me of an early crystal reports viewer problem, which they fixed a long time ago...|||Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...|||

Spivey wrote:

Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...

what does next release meant , is it fixed in sp2 2005.

|||

No, its not fixed, but I figured out a solution. The next release will coincide with the next release of SQL Server - 2008 sometime.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1771550&SiteID=1

|||

What is wrong with the people at Microsoft? Just when you think they have done something right, they screw up something like this!

WHY WOULD ANYONE WANT TO IGNORE THE PAGE BREAK IF IT IS VISIBLE?!

Ugh!!!!!!!!!!!!!!!!!!!!!!!!!

Paging issue on conditionally set second table visibility

Hi. I am having a problem with a 2005 report that has two tables and is designed thru visual studio. The second table is set to page break before printing and also to repeater headers on new pages. It works fine just like that. However, if I place a condition on the visibilty of the table based on an input report parameter it does not page break before rendering the table. In fact it does not page break at all leaving me with an extremely long last page. The visiblity parameter does properly toggle. This is all occurring when rendering the report to the screen using the windows reportviewer. When I export to PDF it looks fine.

Any help would be great.

This is currently by design - when the visibility property is expression-based, the page break is ignored. We are considering changing this behavior in the next release.|||

Thanks for the reply Fang.

I do hope you consider chaninging it. I can understand ignoring the page break when visibility is false but I am not sure why one would want to ignore it when visibility is true. Also, the way it is now the rendered report is not consistent between the screen and PDF.

|||Thanks so much for posting your problem. We are converting from crystal to reporting services and have been experiencing this same issue and were very puzzled. This "by design feature" is making a lot of our reports look very inconsistent with pagination between the viewer and printer or pdf. Reminds me of an early crystal reports viewer problem, which they fixed a long time ago...|||Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...|||

Spivey wrote:

Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...

what does next release meant , is it fixed in sp2 2005.

|||

No, its not fixed, but I figured out a solution. The next release will coincide with the next release of SQL Server - 2008 sometime.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1771550&SiteID=1

|||

What is wrong with the people at Microsoft? Just when you think they have done something right, they screw up something like this!

WHY WOULD ANYONE WANT TO IGNORE THE PAGE BREAK IF IT IS VISIBLE?!

Ugh!!!!!!!!!!!!!!!!!!!!!!!!!

Paging issue on conditionally set second table visibility

Hi. I am having a problem with a 2005 report that has two tables and is designed thru visual studio. The second table is set to page break before printing and also to repeater headers on new pages. It works fine just like that. However, if I place a condition on the visibilty of the table based on an input report parameter it does not page break before rendering the table. In fact it does not page break at all leaving me with an extremely long last page. The visiblity parameter does properly toggle. This is all occurring when rendering the report to the screen using the windows reportviewer. When I export to PDF it looks fine.

Any help would be great.

This is currently by design - when the visibility property is expression-based, the page break is ignored. We are considering changing this behavior in the next release.|||

Thanks for the reply Fang.

I do hope you consider chaninging it. I can understand ignoring the page break when visibility is false but I am not sure why one would want to ignore it when visibility is true. Also, the way it is now the rendered report is not consistent between the screen and PDF.

|||Thanks so much for posting your problem. We are converting from crystal to reporting services and have been experiencing this same issue and were very puzzled. This "by design feature" is making a lot of our reports look very inconsistent with pagination between the viewer and printer or pdf. Reminds me of an early crystal reports viewer problem, which they fixed a long time ago...|||Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...|||

Spivey wrote:

Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...

what does next release meant , is it fixed in sp2 2005.

|||

No, its not fixed, but I figured out a solution. The next release will coincide with the next release of SQL Server - 2008 sometime.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1771550&SiteID=1

|||

What is wrong with the people at Microsoft? Just when you think they have done something right, they screw up something like this!

WHY WOULD ANYONE WANT TO IGNORE THE PAGE BREAK IF IT IS VISIBLE?!

Ugh!!!!!!!!!!!!!!!!!!!!!!!!!

Paging issue on conditionally set second table visibility

Hi. I am having a problem with a 2005 report that has two tables and is designed thru visual studio. The second table is set to page break before printing and also to repeater headers on new pages. It works fine just like that. However, if I place a condition on the visibilty of the table based on an input report parameter it does not page break before rendering the table. In fact it does not page break at all leaving me with an extremely long last page. The visiblity parameter does properly toggle. This is all occurring when rendering the report to the screen using the windows reportviewer. When I export to PDF it looks fine.

Any help would be great.

This is currently by design - when the visibility property is expression-based, the page break is ignored. We are considering changing this behavior in the next release.|||

Thanks for the reply Fang.

I do hope you consider chaninging it. I can understand ignoring the page break when visibility is false but I am not sure why one would want to ignore it when visibility is true. Also, the way it is now the rendered report is not consistent between the screen and PDF.

|||Thanks so much for posting your problem. We are converting from crystal to reporting services and have been experiencing this same issue and were very puzzled. This "by design feature" is making a lot of our reports look very inconsistent with pagination between the viewer and printer or pdf. Reminds me of an early crystal reports viewer problem, which they fixed a long time ago...|||Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...|||

Spivey wrote:

Yeah, I would consider really hard changing that! The master-detail report I spent 2 days on is completely useless because it loads entirely on one page and takes forever. Now I have to rewrite it in Crystal...

what does next release meant , is it fixed in sp2 2005.

|||

No, its not fixed, but I figured out a solution. The next release will coincide with the next release of SQL Server - 2008 sometime.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1771550&SiteID=1

|||

What is wrong with the people at Microsoft? Just when you think they have done something right, they screw up something like this!

WHY WOULD ANYONE WANT TO IGNORE THE PAGE BREAK IF IT IS VISIBLE?!

Ugh!!!!!!!!!!!!!!!!!!!!!!!!!

Paging & Visibility?

I have been trying to figure out why paging was not working on my
reports. I checked the report layout and could find nothing wrong.
Then I started turning off "features" and found that if I use this
statement in the Table Visibility box
"=IsNothing(Fields!CampaignMasterName.Value)" (w/o quotes) that paging
is completely turned off.
Why does this affect my paging? I use this statement so that nothing
is shown on startup of report, headers/footers. Any solutions would
be appreciated.Any conditional visibility disables page breaks. We hope to make
expression-based conditional visibility (but not toggle-based conditional
visibility) compatible with page breaks in some future version.
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0407200612.238843d0@.posting.google.com...
> I have been trying to figure out why paging was not working on my
> reports. I checked the report layout and could find nothing wrong.
> Then I started turning off "features" and found that if I use this
> statement in the Table Visibility box
> "=IsNothing(Fields!CampaignMasterName.Value)" (w/o quotes) that paging
> is completely turned off.
> Why does this affect my paging? I use this statement so that nothing
> is shown on startup of report, headers/footers. Any solutions would
> be appreciated.

Pagination issue in SQL SERVER reporting services 2005

Issue: Page breaks in the following kind of reports are ignored :
Reports having matrix controls
Sub-reports having conditional visibility
Scenario:
What happens is that if a letter has 3 pages then in report viewer it is
showing all the 3 pages in 1 page itself. But it would actually show 3 pages
in print preview. So this problem is only when the report is viewed on the
screen and not with the print preview. So while printing it takes 3 pages
which is fine. But the display on report viewer control is the issue.
Investigation:
The following are a couple of approaches tried :
1. Use the expression =Int((RowNumber(Nothing)-1)/25)
2. Place your matrix inside a â'listâ' control and add a grouping with
the following expression =Ceiling(RowNumber(Nothing)/20)
3. Installed SQL Server 2005 service pack 2 and checked if this can
solve the problem. But it did not help.
Can someone tell me how to fix this pagination issue ?I see nobody has responded to this, so I'm going to throw in my six-penny
worth - but I'm relatively new to Reporting Services, so please don't take
this as gospel. I have observed similar behaviour myself, and this is using a
list control rather than a matrix. I came to the conclusion that it was just
part of the behaviour of the report viewer. In fact if you are trying to lay
out a report to a specific design the report viewer can be a very frustrating
tool. In my case it didn't matter since we had already taken the decision
that all reports were going to be in PDF format, and this displays everything
just fine. I would recommend that you do the same.
John
"selva" wrote:
> Issue: Page breaks in the following kind of reports are ignored :
> Reports having matrix controls
> Sub-reports having conditional visibility
> Scenario:
> What happens is that if a letter has 3 pages then in report viewer it is
> showing all the 3 pages in 1 page itself. But it would actually show 3 pages
> in print preview. So this problem is only when the report is viewed on the
> screen and not with the print preview. So while printing it takes 3 pages
> which is fine. But the display on report viewer control is the issue.
> Investigation:
> The following are a couple of approaches tried :
> 1. Use the expression =Int((RowNumber(Nothing)-1)/25)
> 2. Place your matrix inside a â'listâ' control and add a grouping with
> the following expression =Ceiling(RowNumber(Nothing)/20)
> 3. Installed SQL Server 2005 service pack 2 and checked if this can
> solve the problem. But it did not help.
>
> Can someone tell me how to fix this pagination issue ?