>It almost works, but I forgot to mention that I only want page 2 to print if there is something in the memo field. (I didn't bother with =AFIELDS() because I found that cString went way over 254 characters. There seemed little point in making cString1, cString2 etc.) I also discovered that I would get a "not UNION compatible" error if I tried to use SPACE(254), SPACE(4), or "" as memo, so I put the memo field "as is" in both parts of the SELECT. In order to get rid of unnecessary page two's, I added a WHERE !EMPTY(memo) to the second SELECT. That clause gave me a cursor which only repeated records that had !EMPTY memos. I put all my text fields in the group1 header and put the memo field in the group2 header. However, the report still insists on printing the group2 page for every record, even though most of these records have an empty memo and listorder=1.
>
>I don't understand why FoxPro doesn't make it easier to do this. I should think a multiple page per record fixed-format report would be a routine task.


you should be able to tell the report to erase the line if the memo field is blank, but if you're forcing the memo field (group2) onto a second page, there may be trouble.