>>>>Hey, if memo is empty just filter it when you UNION SELECT!
>>>I did that. I have SELECT ALL keyfield,1 AS listorder,field1,...memo,field10...INTO CURSOR tmpreport UNION SELECT ALL keyfield,2 AS listorder,"" AS field1...,memo,field10..WHERE NOT EMPTY(memo)
>>>That worked. I have a cursor with mostly records that have listorder=1. Wherever Memo was not empty, there is a similar record following with the same keyfield value and listorder=2. However, my report insisted on printing the group 2 page even when the memo field and its label were made PRINT WHEN NOT EMPTY(memo) and REMOVE LINE IF BLANK.
>>>I did come up with a somewhat ugly solution. I used the cursor as above, and put everything in the detail band. Every field and label that goes on page one is PRINT WHEN listorder=1 (which I did one at a time, because I didn't know a way to change them all at once). The comment field and label are PRINT WHEN listorder=2 and are placed right on top of the other stuff in the detail band, which looks ugly in the Report Designer but prints fine. But I have to believe that there is a better way.
>>
>>This way is exactly what you need. Don't worry about 'overlapped' design form. I remember some reports with 3-4 layers of stacked controls.
>
>And one of those reports with 4 layers was mine (not that you ever SAW it, Edward). It worked like a charm but was HELL to modify. Reports need objects. We could have put each 'layer' into a container.
>
>Barbara

Yes, I admit that some 'stacked' reports, I wrote, became hell for people modified them later on. BTW, I am pretty close to start using Crystal Reports for VFP.