We are having some trouble with IBObjects, hope somebody on this list
can give some clues :)

On a dataset we have enabled Pessimistic locking to prevent
concurrent edits to some data, and IBObjects correctly warns about
locking conflicts when that happens. But, when the dataset enters
edit state the next time, it does not perform a cache refresh before
the data is edited (even if cache sync is set to before edit).

The outcome of this is catastrophic, the user that first get the lock
conflict is overwriting the updates made by the other user on his
second attempt to post changes.