A Refresh() in the InteractiveChange() event could work, given that you fire it only once the edit mode start and not everytime the user type something. It might be confusing to the user, though if the current control he had started typing in change value suddenly because it was modified by another user.

IMHO, when using pessimistic buffering, an edit button is almost a necessity. That's one of the reason I kind of favor optimistic buffering.

>A good suggestion, but I like the functionality of an implicit edit, as soon as the user types something. I do have a method that's called from each object's InteractiveChange that enables/disables the Save/Cancel buttons and I could probably just do Refresh() from there. In fact, I was thinking along those lines last night, but got bogged down with the CURVAL()/OLDVAL() issue and forgot where I was initially going with the whole process. I'll try the refresh() at that point and see if that works.