How can I prevent simultaneous updates of the same database record?
When a user employs a standard update transaction (e.g. Update1) this will read the specified database record, show the current values on the screen so that changes can be made, then apply those changes to the database when the user presses the SUBMIT button. However, It is possible for a second user to update the same record in that time interval between the ‘read’ and the ‘update’ of the first user, and if they have changed the same field to different values then the values in the earlier update would be overwritten by those in the later update. This is normal behaviour. If it causes a problem the first question that should be asked is “Why are two users trying to update the SAME fields on the SAME database record to different values?” This clearly points to some sort of breakdown in the administrative procedures. If there is a genuine need to force the system to prevent simultaneous updates of the same database record then this option can be turned ON for particular database tables
