If you mean that you run the report overtop of a cursor, then I already do that. The initial code selects out the data into a cursor and then the REPORT FORM...runs overtop of the cursor.

Thanks.

>One of my rules is to never run reports from tables, run them from cursors instead.
>
>>Hi all,
>>
>>Some users have reported to me that when running "mid-day" reports for their sales, that some of their sales are not showing up in the report. They reported this behaviour:
>>
>>- they go into the report writer and run their sales report. Certain sales that have taken place in the last couple hours are not in the listing.
>>- but then they told me that if they *immediately* run the report again (they do not exit the report writer etc), they get the correct result
>>
>>I tracked it down to some sort of delay if they have had the app open all day to that point or not. That is, if the app has been closed and they fire it up and go the reports screen, they will get the up to date results. But if they perhaps opened up the app at 10:00 am and were working through the day as others put in some sales, then when they go to run the report, it does not show the sales between the time they opened the app and the time they ran the report.
>>
>>- My app keeps tables open in a default data environment after they have been opened for the first time. This was done for speed so that the app was not constantly opening and closing tables on the network.
>>
>>Is this a network thing or is VFP just not refreshing the data when it does a query? Do I need to close all pertinent tables before allowing them to run the report writer?
>>
>>Thanks,
>>
>>Albert