Liveware Publishing Support Forum

Help...__i have a report which i^m printing double sided. The page resets at every Vendor Group.____there are about a million logical lines in the Vendor Group footer which print for various reasons. sometimes none of them print for a given vendor, sometimes a whole page of them. these are followed by a New Page Vendor Group Footer line which is logical to print only if the page number is Odd [mod(mypage,2)<>0], which is then followed by a Vendor Group Footer line which says, "This page intentionally left blank" and is logical to print on True [iif(mypage=2.or.mod(mypage,2)<>0,.t.,.f.)]____my intention is that if the Vendor^s Group is an odd number of pages, a final blank page is inserted so that page 1 of the next Vendor isn^t printing on the BACK of the previous Vendor^s stuff...____simple so far, right? and it works FINE too, UNLESS there print enough of those logical Vendor Footer lines to push it over an extra page. When that happens, the New Page line shoots off incorrectly on an even page AND the "intentionally left blank" stuff prints incorrectly on that next odd page (it should ONLY print on an even page)... and consequently every Vendor Group following after that starts and ends on the wrong side of the paper. aaaaahhhhhh!____any ideas?

Can you create a calc field that returns a numeric 1 for each printing line condition so that you can know when you have exceeded the number than causes things to work?____Other than that, I cannot thing of a good way to get this to work.________Kathleen__R&R Support

huh. i guess i could do that, but of course i^d have to count the header lines, record lines, and footer lines and then add them all up because, of course, every section of the report has all sorts of conditionally printing stuff in it... and who^s to say that any condition based on such counting would be evaluated any more correctly than the page number logic?____i see now that the field information didn^t print in my original post. the field which is evaluating incorrectly when the footer bumps over to an extra page looks like this:____iif(mod(page(),2)<>0,.t.,.f.____and the Group Footer New Page Line is logical on True.____if it worked right, then a new page would be created ONLY when that group footer line appears on an odd numbered page, right? well it works that way only as long as the number of lines in the group footer (ABOVE the new page line) don^t go over the end of a page. if they do, then the new page line shoots off incorrectly on that next page, which is even numbered!____a better solution might be for me to upgrade to R&R (we^re on Arpeggio 2.0) if this bug is fixed in a more recent version... is it?

Version 9 might perform exactly the same.__With group based pagination, R&R does a lot of internal read ahead of records and also enforces some internal widow/orphan control.____One thing that you might look at in your report is in Format Record Layout. If break record area across page is not checked, try checking it and see if that makes any difference.____I would be glad to look at this one for you but would need your report and data in order to test things. Some report problems are difficult to suggest solutions without seeing the whole picture. ____ __Kathleen__R&R Support

kathleen,__i tried checking the "break record area across pages" and that didn^t change the problem.____as much as i would like help, the data in our database is sensitive medical records and i don^t currently have an inocuous test database available so i can^t send it to you...____i did find an article on your web site about about group footers and page totals and i^m investigating if some of the logic used in forcing the page total to ignore group footers that end on the next page might work with this pagination problem... i^ll let you know if it does.____thanks,__ariel