Hi Peter,
>> Well, we're so used to automatic concurrency checking being taken care of by the ABC classes - and the well-known "This record was changed by another station..." message.
well, yes and no. ABC deals with the situation where two users both open the same record, make a change, then attempt to save the record. It only handles a fairly narrow window period.
It does not, for example, gracefully deal with 2 people changing the same field at the same time (even to the same value.)
In the ABC approach the first one to save "wins", the second person has to cancel.
But you are right, NetTalk does not even both to do this.
>> even connected web apps need some sort of synchronization to handle a two-different-users-trying-to-update-the-same-record-situation.
it does deal with them <g>. The second person to hit save "wins". <g>.
In practice what usually happens is that people don't "change the same record at the same time". Which is why seeing "record changed by another station" is a very uncommon error on a desktop system, and most often means you've made a mistake in the code.
cheers
Bruce