I'm not sure I follow the the question, but if you're trying to set the recordsource of the grid, and/or column's controlsources to a cursor generated by an sql statement, you can't do it unitl AFTER the cursor has been created. If you run the SQL statement a second time, VFP actully deletes the old cursor, then creates a new one. Problem is that now your grid will freak out because for that split second it's looking for a cursor that no longer exists. Solution is to create cursor, set data sources. Before you run second SQL statement remove the data sources, then do the second SQL statment, and put back data sources. Kind of a pain, but it works. There are a zillion other ways to handle this I'm sure. (This is assuming I even understand your question of course)

>We are experimenting with VFP 5.0 right before a conversion from 2.6 for a major app. I noticed that when I sql out to a cursor from several tables, the grid builder doesn't see my cursor as a free table nor can I get it to work by setting properties.
>It works if I do a basic sql, but nothing that has anything extra or more than one table...is this a limitation of VFP?
>e.g., SELE lastname,firstname,zip from STAFF where !inactive into cursor temp.......this does not show up in the builder list of tables.
>
>SELE * from STAFF into cursor temp (this does show up and works)
>
>
>Thanks for any advice.