>That's an intriguing idea. I think I'll try that one. How about this, I have been considering using TRANSACTIONS when the edit starts and either END or ROLLBACK as appropriate when the user hits Apply or Undo. What do you think of that?

Holding a transaction open for the duration of a user wait state is generally frowned upon for several reasons. The most important being that any existing records will be locked for the duration of the transaction, potentially causing contention. There are also several table related operations that will give an error if issued inside of an open transaction. Since windows programs are event driven, it gets messy trying to track what the user is doing to prevent him from trying to do something "illegal" inside the transaction (like click a grid header that automatically indexes by that column on the fly- causing an error).