jwang_3

Hi, I'm trying to prevent orphans in my report whereby a single row gets overflowed onto a new page. To do this I've set up a group and moved my text fields from the Detail band to the group's Header band, and set a value in the "Min Height To Start New Page" field, and checking the "Keep Together" option. This seems to have the effect of bumping a few more rows down to the second page so that they are displayed together. However, if I manipulate just my data and remove a few records, I can get it to move the records that it had bumped back onto the first page, leaving just one single row on the second page. I'm not sure if I'm using this feature incorrectly, or if there's some option that I've overlooked. Any insights into this would be much appreciated. Thanks James

Hi, I'm trying to set up a report that has section headings - which are a field in my data source - such that if the section heading overflows to the next page, it will be appended with "continued". Eg: Page 1: Account Name (Subreport data) Page 2 Account Name (continued) (More subreport data) My current setup is to use a TextField for the account name, and a StaticText element for the "continued" label (which has isPrintRepeatedValues="false" and isPrintWhenDetailOverflows="true"). Unfortunately this means I need to separate the horizontal aignment of these two element as there doesn't appear to be a way to alter the width of the TextField based on the length of the Account Name string. Is there a way that I can make these two elements appear as though they were one string regardless of the length of the account name? Or alternatively, is there some variable I could use to detect when the heading has overflowed onto the next page? Thanks James