Hey everyone, I’m stuck with a tricky problem in SQL Server 2005 Reporting Services. I’ve got a table that needs to be hidden sometimes and have a page break at the end. But it’s not working right!
Here’s what I’ve tried:
- Put the page break on the table. No luck.
- Wrapped the table in a rectangle, with visibility on the table and page break on the rectangle. Still nothing.
- Put both on the rectangle. Now I get page breaks even when the table is hidden!
I know there’s some kind of bug with this in SSRS 2005, but I’m hoping someone has found a way around it. I really don’t want to make a whole new report just for this!
I’ve also tried putting an empty table after the main one with a page break, but that didn’t work either. Even tried nesting everything in rectangles, but no dice.
Any ideas? I’m running out of options here!
I’ve faced similar challenges with SSRS 2005, and I understand your frustration. One workaround that has worked for me is using a combination of a rectangle and a line. Place your table inside a rectangle, set the visibility on the rectangle, and add a line below the rectangle with the page break property. Then, link the visibility of the line to the same expression as the rectangle. This approach often bypasses the visibility-pagebreak bug in SSRS 2005. If that doesn’t work, consider using a matrix instead of a table, as matrices sometimes handle these properties more reliably. As a last resort, you might need to create a custom code function to manage the page breaks programmatically, but that’s more complex and time-consuming.
ooh, intresting problem! have u tried using a subreport? it might help bypass the visibility/page break issue. you could put ur table in a separate report and then call it as a subreport in the main one. that way, u can control visibility and page breaks separately. just a thought - might be worth experimenting with? let us know if it works!
hey lucaspixel, i feel ur pain! ssrs 2005 can be a real pain sometimes. have u tried using a list instead of a table? lists are more flexible and might handle the visibility/page break combo better. also, check if ur dataset is returning empty rows - that can mess things up. good luck mate, hope u find a solution!