>Another reason is to notify a user that a record they are about to update has already had its original value changed by another user. That user can be notified of the new value and given a chance to abort their change or go ahead and overwrite the other user's change.

Hi Mark,

I'm assuming that you're talking about optimistic buffering here. I'm having a problem devising a way to trap this using pessimistic buffering. Do you have any suggestions? I posted a question here today (or was it last night) about this (I forget the topic name).

TIA,
Bonnie