Duplex Printing Requiring Blank Page

[rberquist]

I know I have seen this topic before but I can't locate it. I need to print a blank page if a group ends on an odd page number. This is a common issue when printing a report in duplex format that has to be separated and distributed to different recipients. What is the best/common practice with iReport to accomplish this. A blank page would be best but "This page intentionally blank" on a page with header/footer is acceptable. Thanks for any help.

Bob

iReport 3.7.1

Post Edited by rberquist at 04/01/2010 01:29

[happi]

Hello,

 

I have the same problem. Can anyone tell me how to do that?

 

I am using iReport 2.0.5

 

Best regard

happi

[slow]

You can insert in the GroupFooter a print when expression like:

new Boolean($V{PAGE_NUMBER}.intValue()%2==1)

and insert into this band a page break...

so, if the band is printed, then there is a page break...

see attached files...

(i use italians name for testing :) )

 

 

____________________________________
if it works... give me KARMA points please!    : ) 
 

 

[rberquist]

slow...

Thanks for the response.  I do use the the method you suggest for generating the "This Page Intentionally Blank" message on an extra page to satisfy the duplex requirement. However you still get column and page headers so you really don't get a blank page. I also add a boolean we name DUPLEX to turn the page on and off depending on the printer thus avoiding the extra page when not printing to duplex capable printer.

($P{DUPLEX} == true) & ($V{PAGE_NUMBER} % 2 == 1)

Putting everything in generated groups and avoiding builtin groups such as column, page .. etc is a possibility but you give up a lot of productivity. One of the reasons for using iReport.

I think to handle the duplex report as a blank page iReport would have to expose the next and possibly previous fields in the result set for the report. I would think that the next fields must be present for the bands to work.

The other option is to include them in the query. This runs into the issue of analytics in the query, easy to write (at least in oracle), expensive to run, especially if the you are talking about a view used elsewhere many times.

Anyway for now my column header print when expression remains empty.

Thanks,

Bob