Well, View approach is preferable in many ways. Your application can easily change back-end, if needed, if you would use views instead of tables. So, in general this advice makes a lot of sense.

Hovewer, for a quick fix this solution is fine.

>Hi Nadya
> I have done just that and it has worked fine, thank you. So I guess I don't have to set up a View. Should this code be run before every update to the query cursor, it seems like it should.
>
>Regards,
>Carmen
>>>When a SQL statement is issued and the results directed into a table, what happens when the statement is run more than once? I have a grid which uses as its source a table generated by a SQL statement. When a record within the grid is selected, another form is launched which works with the data generated by the SQL statement. Upon returning to the initial form, I run the SQL statement again so the grid will reflect the changes made to the data. When I do this however, the grid is blank and nothing is displayed. Have I somehow created a second table when the SQL statement is run again?
>>>
>>>Thanks in advance,
>>>Carmen
>>
>>In order to avoid this problem you have to do:
>>
>>this.grid.RecordSource="
>>select ... into myTable
>>this.grid.RecordSource = 'myTable'