Hi Wendy,

Nice idea. Tried it, however the change in the selected table happens within the REPORT FORM command which I can't trace into.

Thanks anyway

Liam



>What about running a trace with a breakpoint in the Watch window on SELECT()?
>
>>No. I scoured the .FRX looking for anything that might have snuck in but it's empty
>
>>>Do you have anything in the report's environment?
>
>
>>>>Hi all,
>>>>
>>>>I have an odd problem with the reporter that someone may have come across before. Any ideas very welcome...
>>>>
>>>>Situation
>>>>1) Numerous tables open...
>>>>2) SELECT blah blah blah into cursor CurRep
>>>>3) REPORT FORM blah blah blah
>>>>4) Report is fine until I move to the next page or zoom in or out then
>>>>I get an error message not found
>>>>
>>>> is one of a few variables in the report that is causing the error.
>>>>
>>>>After investigating (and much hair pulling) I discovered that VFP is SELECTing a table other than the result of the SQL statement (CurRep) DURING the report!
>>>>
>>>>Before the REPORT FORM command I inserted a messagebox(alias()) command to confirm that the correct table is, in fact, selected. A further messagebox(Alias()) command after REPORT FORM (and usual errors) will show that a completely different table is selected.
>>>>
>>>>Explicitly SELECTing the Cursor after the SQL statement makes no difference.
>>>>
>>>>During debugging I also discovered that if I issue a BROWSE before the REPORT FORM command, everything will go fine and the correct table will remain selected.
>>>>
>>>>Anyone seen anything like this before ??
>>>>
>>>>TIA
>>>>
>>>>Liam

Liam O'Hagan
MCP VFP Desktop Apps