>>>>>>Is it possible to print two pages within a band?
>>>>>>
>>>>>>advTHANKSance
>>>>>>
>>>>>> ...kt
>>>>>
>>>>>Do you have a problem that band is too big, bigger than page? There is >workaround here too.
>>>>
>>>>I shudda known. Lay it on me Ed! The situation is that I have
>>>>a report (same report) that when I get a break on the primary key
>>>>(provider id), I need to print two separate pages -- a letter of
>>>>intoduction (mostly prepared text, some data from my table) and
>>>>an invoice.
>>>>
>>>>What say U?
>>>>
>>>> ...kt
>>>
>>>The genric way to print the same record on two pages is following:
>>>1. Inflate your data making two record from each one.
>>>Select recno() as Recno, 1 as Lstorder, * From Table1 Order by 1,2 ;
>>> Union Select recno() as Recno, 2 as Lstorder, * From Table1
>>>2. Group your report form by Recno,Lstorder providing 'Start Each Group on a New Page'.
>>>3. All detail band fields should use 'Print When' clause evaluated by Lstorder, i.e. some fields will be printed for Lstorder=1 and others for Lstorder=2
>>
>>So then in the band I will pro'ly have fields displaying on
>>top of each other, but when I actually print(preview) only one
>>will print, correct?
>
>Correct.
>
>>What about the fact that the band sizes will be different? Won't this
>>throw of any lines bound to the bottom of the band?
>>
>> ...kt
>
>You could bind fields to the top of the band.

One more "what about", what about line counts? I have a report
now that I use a similar strategy on, althought I use it more for
printing headers on a page, i.e there are no overlaping fields.
It appears that the line count gets goofed up and it doesn't take
into account that the header lines will not be printed on the page
if my condition isn't true (I only print the header for the first
address) and breaks after printing only two addresses.

Have you ever experienced this? Is there a system variable that I
can modify to reset the line count or something?