Hi,

If user A changes an important field in a record (invoice state for example)
while user B is editing that same record, alle changes made by user A will
be overruled when user B updates that record.
This could cause serious problems, because user A must be sure of the
results of the update query.

There are several solutions:
-msaccess will not allow to update a record "changed by another user". That
works great
-dbexpress will only put "changed" fields in the update statement, thus
merging the two changes.

But what is the correct solution for this problem using IBobjects? Is there
a way to only put "changed" records into the update statement.
If no, what to do ?

-you could allways use pessimistic lockings, but it will block the system to
much with more than 30 users
-you could make the most important fields "read only" preventing IBO to use
them in an update statement, but that's not 100% safe.

Leon