>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.

Yes, that's the way it currently fires the Save/Cancel enable method, only once at the start of the edit mode.

>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.

I know it might be confusing, that is why I was looking for some way to detect that the record had been changed so that I could notify the user of that prior to doing a refresh(). Any other ideas on how to trap for this?

Bonnie