Dmitry,

Looks like Marcia gave the the answer. I would say that something is happening to the cursor which causes the grid to loose its mind. I don't see how you are getting the data from Sql Server but if you are using SQLexec() then the cursor is closed and a new one is created each time you run it.

>First, thank you for your message.
>
>The approach with zapping the cursor won't work. This is a buffered cursor and you can't zap it. And you can't Delete All and Pack it either because it is a remote table.
>
>If I understand you correctly and you mean "setting record source = space(0)" of the grid, I think this will make the grid lose all its properties.
>
>What I don't understand is that there is no "new data" for the grid, the RecordSource of the grid does not change.
>
>>This has been this way since I can remember. One possibility is to set the recordsource = space(0) before the cursor closes and the setting record source = "yourcursor" after the new data arrives. If this doesn't work then you can zap the cursor and load the new data into another cursor and then append from new cursor into old cursor.
>>
>>>I have a form with pageframe. On page 1 fields are bound to a view/cursor A. On Page 2 there is a grid bound to a view/cursor B.
>>>If the code closes cursor A and gets a new one from SQL Server (based on some user defined conditio), the grid on page 2 loses all properties. Actually the grid on Page 2 becomes blank (no columns, no rows). Note that cursor B has nothing to do with cursor A.
>>>
>>>Is this a bug or this is the way it is supposed to work?
>>>
>>>Thank you.