>David,
>
>Had a similar problem to yours, MSFT (A) did not understand it and (B) never resolved it.
>
>On the form there was a list box filled by a SQL query and an adjoining grid, attached to a cursor filled by a SQL query. The click even in the list called a SQL statement which filled the cursor. The variable passed to the SQL was "lcwhich_tech". Click, click, click on different names and the grid filled with the related information. TABbing to the grid or CLICKing on it generated the error "Variable lcwhich_tech not found". The grid DID NOT NEED the variable, it had been disconnected from the source cursor to the dummy cursor while the SQL executed and then reconnected.
>
>What really teed me off was that this was textbook-perfect code, everything passed by variables properly scoped, etc., and VFP returned this crap.
>
>Solution? Make lcWhich_Tech a variable scoped to the form, essentially making it global. Yuck!!
>
>Small consolation, but hope this helps - Miles Thompson
>
>
Hi Miles,

Thanks for your response, but, unfortunately, it doesn't help. My SQL-filled control does not use any variables. In fact, in one instance of this problem, the drop-down list pulls the data directly from the table. But it crashes on the same item that the SQL-populated control crashes on.

MS continues to offer little help. I think they have a fundamental problem that they know nothing about. Maybe 6.0 will be better -- or worse.

Thanks -- David Anderson