Don,

Nick had good advice, but if you are only using a few fields from CursorB, then why not include them in CursorA? I've found that keeping the report DataEnvironment empty and SELECTing the cursors in either the calling program or in the Report INIT() method helps avoid these problems.

HTH
Barbara

>I have a strange one with previewing a report. I have two cursors created prior to previewing a report. CursorA holds details, CursorB holds summary data (like invoice details, invoice header). With the detail CursorA being the primary to run the report, if I try to click on arrow to advance to next page, the report preview changes the alias to CursorB.
>
>THIS IS WITH VFP5, not 6
>
>There are no SET RELATIONS, no indexes, just straight details in CursorA and a single record in CursorB.
>
>Any ideas??? I didn't see anything from history
>TIA