J
John
An idea to think about is the record locking for edited
records on the forms property list. This way if a person
is in editing the record, nobody can edit the record until
that person is done. The locking only occurs on the
record, not the table.
Good luck.
John
out the other changes.
record again and compare every column to see if it has
changed, but that would create incredible overhead. Or I
could just save the original update date stamp and if it
has changed, inform the user. Ideas?
records on the forms property list. This way if a person
is in editing the record, nobody can edit the record until
that person is done. The locking only occurs on the
record, not the table.
Good luck.
John
same record, the last person to save their changes wipes-----Original Message-----
My system is multi-user and all processing is done with unbound controls.
The problem is that when multiple users are updating the
out the other changes.
record read and then just before the INSERT to read theIs there any way to handle this?
Currently when a record is updated the process is:
(1) User requests a record
(2) Record is read and moved into unbound controls
(3) User requests 'update'
(4) Record is written with INSERT from unbound controls
The only thing I can think of is to save the original
record again and compare every column to see if it has
changed, but that would create incredible overhead. Or I
could just save the original update date stamp and if it
has changed, inform the user. Ideas?