>Instead of using a filter, you can use a view. Using a filter on a Grid is slow, anyway. I heard rumors that this was improved in VFP 9, but I am not sure how trustworthy this is.
>
>A view will show you only the relevant records.
>
>If a user deletes a record in the view, you would probably still see the gap, until the next time the view is refreshed.

Hilmar,

You misunderstood the problem. I'm using a cursor (read-write) as a record source for the grid. Originally every time user resolved an account, I re-built the cursor. But yesterday I realized (with my colleague), that I don't have to do this (made a trip to the server), I can just delete the record from the cursor. However, as you know, with SET DELETED ON the deleted records act as a filter and then we have all this weird behavior of the scrollbar. I have a possible solution in mind - in the DeleteRecord method after I deleted records select them to a temp cursor, zap the original cursor and append from the temp... May be I should try it..