binding - grids: yes... controls: no

Nothing is purged... the update batch tells ADO to take the entire recordset and send it to the database. Update only works on the current row. That's the difference.

locktypes - I don't know, but I think they are right.

events - I wondered about that after I posted. With disconnected recordsets, I'd simply set a dirty flag.... then enable/disable a save button based on that flag, and when the form closes, check the dirty flag, and if it's set, then prompt to save....

But now that you've mentioned it, if the user can only work with one record at a time, it might work better to only bring back one record... the one being edited.... then when they move, save the changes, get the next or previous record... meh... depends on how the app is set up and what you want to do with it exactly.

-tg