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!!!!!!!!!!!!!!!!!!!!!!!!!