>Hmmm, I can't imagine the CursorRefresh doing both a REQUERY and TABLEUPDATE. I would look in the BeforeCursorRefresh method to see if the TABLEUPDATE is done there.

When I added new record to the cursor (INSERT INTO cursor_name...) and then called CursorRefresh. It updated the table by adding new record to the table. Is this wrong and should some other method be used instead of?

>I would stick with the CursorRefresh instead of Requery because CursorRefresh is functionally the same as a REQUERY on a view, it just that it is designed especially for the CA.

OK

AT