>>>>Jaime,
>>>>
>>>>Besides what Neil has suggested you can also use a "safe-Select" approach for your grid. To do this you establish a cursor with the CREATE CURSOR command to be the record source for your grid. Then when you need to refresh the data you can;
>>>>
>>>>

>>>>SELECT ... FROM ... INTO CURSOR MyIntermediateCursor
>>>>SELECT MyGridCursor
>>>>ZAP
>>>>APPEND FROM DBF("MyIntermedaiteCursor")
>>>>

>>>>
>>>>This prevents the grid from losing its setting whenteh cursor is blown away by the SELECT SQL command.
>>>
>>>Thanks Jim. I don't think ZAP will do it though, it's multiuser...
>>
>>In Jim's suggestion, the myGridCursor would be a local one, so you could Zap it since there are no multi-user issues involved.
>>Another alternative might be using parameterized Local Views.
>
>Even then you would still use ZAP to get an empty cursor.
>
>http://my.advisor.com/doc/SILVL14-01
___

You would not zap prior to a requery()