Does your grid match all of the criteria listed below.

1. Is based on a cursor.
2. The cursor gets reset by a sql-select statement.

I have also had to save the recordsource to a variable, change it to point to a dummy cursor, perform all the necessary updates, change the recordsource back to the correct cursor, and then fix all of the columns, headers, etc.

Not the best answer, I know, but I haven't found a better way. Perhaps someone else will weigh in.

>The "go top" and refresh the grid did not do it.
>
>But I did come across this: It works, but the wrong data appears in the grid.
>
>
>PRB: Cursor-Based Grid Goes Blank If SQL SELECT Resets Cursor
>
>SYMPTOMS
>If a grid's RecordSource property is set to a cursor, and then the SQL SELECT command resets the cursor, the grid appears blank if the RecordSource property is not set back to itself.
>
>The following command will refresh the grid properly if a SQL SELECT is run to rebuild the cursor, but if the grid's column or header properties have been customized, these customized changes will be lost and the grid's column and header properties will change back to their default settings:
>
> THISFORM.GRID1.RECORDSOURCE=THISFORM.GRID1.RECORDSOURCE