Hello, For a long time we have been having problems with printing carry over values. A valid carry over value is essential to many of our customers. As I can see, there are some posts in the forum from 2008 and some bug reports that are still open. To remind you that this problem still occurs, I will attach a sample layout with an xml data source that shows the carry over problem on page 2 of the pdf document. This sample is very simple. In customer installations we have layouts that are much more complicated (more bands with subreports and so on). For printing the carry over value we calculate all necessary values (the current value, the next value and the previous value). The main problem is to decide which value we have to print in the page footer, because at render time we have no information on whether a field is printed on the current page or is moved to the next page in case of an overflow. We were thinking of "minHeightToStartNewPage", but this does not fix the problem in all cases. Another thought was to prevent bands from splitting (set "split allowed" to "false"). But this would end up in printing each position to a single page with much white space at the bottom of the page. So this is not a solution. Having a flag that marks a field as a "carry over field" might be a solution to this problem. The renderer should set this flag if the field is printed on the current page. In this case we may ask the field, that is responsible for our carry over, if it is printed on the current page and are thus able to print the valid value. What do you think? What other possibilities do we have to print a correct carry over value? Does it make sense to open a new feature request/bug report? Regards Marcus