Page Numbering dilemna
Posted: Fri Feb 25, 2005 4:37 pm
While I^ve been able to get a huge performance increase by restructuring a report to run from a single control file record, it^s left me with one problem I haven^t been able to solve yet. The report now effectively consists of a few hundred "sub-reports", each of which needs its own page-numbering range. This is complicated by the fact that each sub-report is drawn from 1 or two composite records, and prints one page for each record, plus one final page.____The problem is that static page numbering is proving unworkable, due to the large number of permutations of the number of lines that actually print on each page. (About 150 of the calculations used are involved in logical fields that can suppress band lines.) So, I^m stuck with using the same footer band to print page numbers for all three of the sections, but no way to know which of the three sections is causing the footer to print. What I need to make this work is any one of:____ 1) A way to reset the page number back to 1. I can use the Previous function and compare some fields to know when it^s time to do that, so this would be the easiest way - doesn^t seem to be possible though - is it?____ 2) Anything remotely resembling a variable, whose value can be modified by a calculated field. I tried using Stuff(), but it seems that this function only returns an altered string, and has no affect on the field named in the function call - is that the case? Is there any way to have a calculated field actually modify the contents of another field?____ 3) A way to position a field at an absolute vertical position, or relative to the page bottom. That way I could lose the footer, and just have separate static page number lines for each section.____At this point the only alternative I can see is three CDLL calls, but I don^t want to go to that extreme until I^m sure there^s no simpler way. Any suggestions?____Thanks,__Mike Brumley__