To get the UI we required, we built a custom .NET front end that
communicates directly with the MSRS web service. Paging (e.g. a break in the
data at a certain point with some indicator for the "next" page) does not
seem to work once you take this approach. Anyone figured this out?Hi Sean,
> To get the UI we required, we built a custom .NET front end that
> communicates directly with the MSRS web service. Paging (e.g. a break in the
[...]
>does not seem to work once
What doesn't work?
I used the same approch. My user control calls RS webservice with parameter "Section" of device settings so I can _read_ report section by section.
There is only a little problem... there is no way... perhaps is better to say I don't find any way to known How many sections I must paging :o
HTH M.rkino
--
Marco Barzaghi - [MVP - MCP]
http://mvp.support.microsoft.com - http://italy.mvps.org
UGIDotNet - User Group Italiano .NET, http://www.ugidotnet.org
Read my WebLog: http://www.ugidotnet.org/436.blog
Showing posts with label break. Show all posts
Showing posts with label break. Show all posts
Monday, March 12, 2012
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...|||
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...|||
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!!!!!!!!!!!!!!!!!!!!!!!!!
Saturday, February 25, 2012
PageBreak after x items for group, different on first page
I am trying to add a page break for table details after x items with x being different for the first page of report.
I am able to add a page break by adding a group to table with group expression =Int((RowNumber(Nothing)-1)/25). But I can't figure out how to do this where groupexpression on page 1 of report = Int((RowNumber(Nothing)-1)/15) and on all other pages =Int((RowNumber(Nothing)-1)/25).
I tried
=IIF(Globals!PageNumber=1,Int((RowNumber(Nothing)-1)/15),Int((RowNumber(Nothing)-1)/25))
but Globals cannot be used in group expression. I also tried putting group expression in a textbox on the report but it will not let me refer to the textbox.
Any assistance is appreciated!
Chris
references: http://msdn2.microsoft.com/en-us/library/ms157328.aspx , http://msdn2.microsoft.com/en-us/library/ms157328(en-US,SQL.90).aspx
Try a group expression like this:
=iif(RowNumber(Nothing) <= 15, Int((RowNumber(Nothing)-1)/15), Int((RowNumber(Nothing)-1-15)/25))
This should result in 15 rows for the first page, and 25 rows on subsequent pages.
-- Robert
Subscribe to:
Posts (Atom)