>I am using VFP 5.0a. The report uses the wrong cursor the first time the report is printed, but each time thereafter it uses the correct cursor.
>
>To debug, I placed a messagebox in the following DE code events to try to find out when the cursor gets switched (they execute in the following order):
>OpenTables() && reports correct cursor
>BeforeOpenTables() && reports correct cursor
>Init() && reports correct cursor
>
>Sequence of events:
>1] In a PageFrame I have a grid and a commandbutton (cmdPrint).
>2] I select a row in the grid.
>3] I click the cmdPrint that creates the cursor 'curReport' used in the report.
>4] The report is called.
>5] The first time, the report uses a cursor 'tempSort' that was previously opened. (If I close 'tempSort', the report works fine the first time, but other parts of the pageframe depend on it being open.
>6] The second time, the report uses 'curReport' correctly.
>
>I saw some discussion in UT about using a grid. The suggestion was to SetFocus() to something other than the grid. So in the cmdPrint.Click() I have a line: 'This.SetFocus()' [I know this is redundant, but I'm willing to try anything!].
>
>I also searched Visual SourceSafe for any occurance of 'tempSort' in the report, and found no reference. I even opened up the .FRX and looked in every field - 'tempSort' is not referenced.

Hi Dennis,

You've probably looked at this already, but is there anything at all in the Report's Data Environment? What happens if you put a breakpoint on USED("TempSort")?