isoc_dev

Echo, C-Box, You've made me so happy! So, breaks need to be near the end of a band in order to work. If placed them at the appropriate band bottoms (which was awkward: iReport will place a break outside the band when aligning it with the band bottom - I think I'll submit a bug if it's not there yet) and set their position to float. That did it and my pages are broken now (pun intended)! (I think fix relative to bottom and float combined with being positioned near a band bottom are equivalent). Case Closed, I'd say! Thank you all! In case you're an astronomer, please use the upcoming Integral Announcement of Opportunity to see beautiful JasperReports in action, live on a stage near you! ([url=http://integral.esa.int/] http://integral.esa.int )

C-Box, I would by happily posting the failing design, but they require a compatible data source before you could try them. How would I go about that? Meanwhile, I have abandoned the PageBreak approach. "Things" started to behave in a way I can control them by using the 1 pixel title page starting on a new page for every subreport. I am reasonably satisfied with that approach. (I noticed something undesireable re. layout only recently: I don't understand the split allowed flag and it does not seem to control a band to run over the page end while it would fit on a single (new) page. This is a new topic, which I will search for in the forum before posting..)

I get this feeling not being in control re. subreport elements and their size. Here's the deal. I am using the adding-a-group-per-subreport trick to construct a report based on 7 subreports. Every time I add a subreport, I am having trouble getting output. The first 100+ tries I get nothing but an out-of-memory error. The hanging seems to be caused by the band/elemt size I am giving to the subreport. but I really do not understand it. And of course I want to understand, so that I can skip the 100+ useless tries in future. My (not so successful) approach is: - create a band, height 10 - add the subreport, height 10 - print with overflow - fix to top of band - let the sizing be done by Jasper This would allow for 600 / 10 = 60 subreports in one report, before I hit the page size limit, right? But this does not always work, apparently JR requires a certain minimal band or element size. Does anyone the formula to get that size? If the size is less than the magic (to me) mininum, JR will start a new page and see that the report does not fit over and over again until memory runs out...

CBox, I am taking the liberty to post while none of your suggestions seems to solve my quest ;-) Here's what I get: float on the page break does not seem to matter. I reduced my report to include only 2 subreports with a page brake inbetween. The first subreport is repeated on every page! By setting float=true on the subreports, the overstrike is gone. However, the 2nd subreport does not start at the top of the page, it starts just below the repeated 1st subreport! No matter how I tweak the stretch or print repeated values flags, the result is: repeating subreport-1 and very short subreport-2's at the bottom of every page after the first page (which leads to my next post: "sizing subreport elements") My naive expectations of the break element are: - report elements above the break are on pages before the pages that show the elements below the page break and never on the same page - the elements immediately below the pagebreak will be printed as close to the top of a page as titles and headers permit Now these may be completely out of line! Especially since my goofing around shows very different results. Where can I find the correct and official mechanics (except for the source)?

Follow up here: When integrated in my application, after filling the report and exporting it to PDF, the overstrike problem is visible in the PDF too :( ... still hoping for some support

Hi All, If been struggling with pagebreaks for quite a while now. Yesterday, after upgrading to iReport 1.3.0 I discovered the pagebreak/break element and hoped to end my misery in fiddling with the report groups. Here's my observation. I created 3 reports which I'd like to print as subreports in a report; all 3 starting on a fresh page. Hence I place the subreports on the detail band and add 2 breaks, 1 between each. When execute the report and preview, the report pops up in the previewer with the right amount of pages. However when I move through the pages, the preview starts getting messed up: the second report is drawn over the first, and the third over the both of them. Only when the next detail is hit, the page is cleared and a clean display of subreport 1 is seen. Now I wonder: - has anyone seen this effect before? - will this effect disappear when really printing (not wasting trees yet)? - Can I adapt the break element such that the effect disappears? - Am I incorrectly using the break element? - Is it a bug in the previewer? - Is it a bug in the break element? (I've seen enthousiastic reports on its use only, so far... so I doubt it) Thanks for any support, Marnix size=297]http://www.jasperforge.org/components/com_joomlaboard/uploaded/images/irep131_overstrike.jpg size=150]