I was just explaining conflict detection in this thread: RecVersion in PurchTable.
When you switch to another record, the record is saved. The form first calls write() on the datasource, which calls update() on the table. super() in update() calls the kernel logic for saving, which then check if there aren't update conflicts.