>>>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?
>>
>>I don't use line count.
>
>Nor do I, but I think you missed what my question is. In the report that
>we're talking about I use something similar to what you proposed, but I get
>a page break about halfway down the first page. The problem seems to be
>that FoxPro is using the size of the band and not accounting for lines that
>are not printed because of PRINT WHEN conditions.
>
>My questions are 1) have you encountered this before, and 2) can you
>recommend a workaround for it?
>
>I appreciate you time and expertiese Ed. Thank you.
>
> ...kt

It seems to me that we got lost in this thread a little bit. If you use Grouping and each group starts with new page then obviously page break will happen when group expression (recno+lstorder) gets changed.