5
« Last post by egsuh on Today at 08:56:31 am »
I think the program should be designed not to try to edit the same record and field by two or more users simultaneously. Let's assume that user A and user B have opened the same record, and they change the same record and update. Even after user A updated the record and committed, user B is looking at the old data (because it is under different transaction), which is before changed by A. And if the user B update it again, then A's modification would be lost. This is nonsense. So, once A opened a record, B should not permitted to view or at least change the record. If two or more users HAVE to access the same data and modify them (e.g. one person edits unit cost for a product, while another person edit production volume for sales), the two fields should be in different tables. Users can see the whole record combined, but do not edit the same field at the same time.