> I think upWhereChanged better than upWhereAll, because this uses only key

field and fields

> that have changed are used to find the record.

No, it isn't better, unless you don't care about avoiding record update
corruptions. The whole idea by using upWhereAll for cached updates is
because you have taken concurrency/conflict resolution away from the server.
Thus, by having all possible columns of the record in the update statement
will bring to your attention the case where another user has updated the
record and caused an update conflict for you. With cached updates and MIDAS
this is the only way to detect such a case and it is lousy at best.

> Thus if another user changed the same record but it did not change the

field that is being changed by the current user, the update would be
successful.

Not in my book. I know of cases this could apply in and if so,
upWhereChanged would be what you want. I just don't see how this would be
considered desirable.

> And regarding property IB_TransUpdate, what do you think?

I don't recall specifically what you are implying here.

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com