How do you folks handle printing a report that is not a repetitive list?
Lets say I have a report that is not the same thing over and over again, does not have a consistant body, and I need to put the page breaks in different places.
It seems to me that the Printing architecture is designed around a consistant header, body, footer theme with no other alternative.
Like in VB with the Printer Object, you would print some stuff, put in a page break, print some more stuff, etc. If you wanted to print a list you would loop through it, you would not be forced into running the same routine for every page.
Maybe I am just looking at this stuff the wrong way.
An example would be an invoice. It has a header or top section. Then you have a detail section. Lets say the detail section rolls onto a second page. By using PrintPage, you have to globally hold the data and the position so the next call will pick up where you left off. But lets say the detail section was more complex and had several subsections. You would have to track which subsection was currently printing globally then have a case statement return you back to the code that was printing at the time of the page break. And you still have to test to see if you are withing the bounds of the page. It would be easier to just stay in the rountine and throw a pagebreak manually when you needed it.
Lets say I have a report that is not the same thing over and over again, does not have a consistant body, and I need to put the page breaks in different places.
It seems to me that the Printing architecture is designed around a consistant header, body, footer theme with no other alternative.
Like in VB with the Printer Object, you would print some stuff, put in a page break, print some more stuff, etc. If you wanted to print a list you would loop through it, you would not be forced into running the same routine for every page.
Maybe I am just looking at this stuff the wrong way.
An example would be an invoice. It has a header or top section. Then you have a detail section. Lets say the detail section rolls onto a second page. By using PrintPage, you have to globally hold the data and the position so the next call will pick up where you left off. But lets say the detail section was more complex and had several subsections. You would have to track which subsection was currently printing globally then have a case statement return you back to the code that was printing at the time of the page break. And you still have to test to see if you are withing the bounds of the page. It would be easier to just stay in the rountine and throw a pagebreak manually when you needed it.