RTC: Splitting data into 2 pages (with footer on 2nd page) ...

HI,

i am working on a invoice report… In case my invoice data exceed certain lines,the data should be continued in the next page and the total values in the footer must be printed on 2nd page alone…I want to know how to do this in RTC…

My classic output…

Next page

headers must be same for both pages where as footer should print only on second page…In case there are more data in a page it should get carried in the second page …

Any idea frnds…

Did you try these posts

http://forums.asp.net/p/1356470/2784550.aspx

http://www.mibuso.com/forum/viewtopic.php?f=32&t=45487&start=0

i dont think those posts match my need…

It automatically splits the data ( like report:10074)…i am not able 2 get how it is getting splited ,i want to add those text “transferred to page 2” and “transferred from page 1” when it is getting splitted…In preview everything comes in single page,but while printing it automatically splits…

Which localization database are you using? as youa re saying report 10074…

US…10074 -Sales Invoice…

if u c in that,in classic the output will be as i have attched…if u look into rtc output (printed or converted into pdf) those text lines doesnt appear it just splits…

ok got your point…

so you are looking for Transheader and transfooter sections which not directly mapped from Classic reports to RDLC reports

but here are some blogs to achieve your requirement

http://blogs.msdn.com/b/nav/archive/2011/06/06/transfooter-and-transheader-functionality-in-rdlc-ssrs-reports-revisited.aspx

http://blogs.msdn.com/b/nav/archive/2010/03/17/transfooter-and-transheader-functionality-in-rdlc-ssrs-reports.aspx

Thanks a lot…Hope it works…

i tried by looking the forums…still i couldn’t get it…

In that forum they say like this

Question: Would this also work in the example of having a list of sales order lines per sales header and the sales order lines goes to multiple pages?

Answer: The report above is a bit simplified in order to illustrate the point. It can be easily extended to support your scenario. I.e. the key for the hash should include page number AND header no to accomplish this.

can some1 help me out in extending the key for the hash with page and header number ???