Thanks Naomi but the problem is not related to a grid. (I don't think) There are a couple of grids several pages back in a pageframe but they are not visible or active. Plus I specifically set the cursor into a textbox before running the report.

Here's another strange. When the report is run (and showing the wrong cursor) it will produce about 25 pages. However the print preview will not page beyond page 10. Go figure. :(



>Please check FAQ #15515
>
>>I have a fairly simple report that has been working OK for a couple of years. A few days ago we noticed that when converted to a PDF the last row of text in the footer was being cut off. So I modified the report to make the height of the footer a bit larger. NOW for some unknown reason the report is printing data from the wrong cursor and I can't figure out why. The code works OK when run outside of the main program but when run from the application menu it somehow produces data from the main program cursor rather than the one generated specifically for the report. This one has me really stumped. I thought that maybe there was a function that was leaving the pointer in the wrong place but that is not the case. The report does not have a data environment or a private data session. The on error is turned off. I don't know where else to look. Any thoughts? Here is the code.
>>

>>local lcOldFilter, lcOldOrder, thisrec, lnOldWorkArea
>>set reportbehavior 80
>>on error
>>
>>lnOldWorkArea = select()
>>
>>select tip.tip_id, st_name, lead, total_cost, system ;
>>	from tipdatabase!tip ;
>>	inner join tipdatabase!current ;
>>	on tip.tip_id = current.tip_id ;
>>	where current.status = "Active" and (system = "Bicycle" or system = "Pedestrian");
>>	order by lead ;
>>	into cursor crsTemp
>>
>>_screen.visible = .t.
>>select crsTemp
>>
>>report form appendix9 to printer prompt preview noconsole
>>
>>_screen.visible = .f.
>>
>>use in crsTemp
>>select (lnOldWorkArea)
>>

>>
>>Thanks