Thomas,

> What does a full refresh exactly mean? Which IBO method should have been
> called here or is it a matter of closing and re-opening?

This would be like pressing F5 in a grid or calling the Refresh method.
Under the current implementation, unless the IB_TransForUpdate was
committed, it would appear as if the changes already made had been lost.

> Honestly, I'm not sure, but I guess I wouldn't expect to see
> non-committed changes by the IB_TransForUpdate in the read transaction.
> So, if the read transaction is working as read committed, then it simply
> will see committed changes.

Right, which would be confusing because a query wouldn't be reflecting
changes that were performed by way of its own Edit, Insert and Delete
methods.

> I'm not sure either, if I would like to see non-committed changes anyway.

A possible solution is to take advantage of the cached updates
functionality. When the dataset is refreshed, even though it will get the
old data from the server, I can make it respect all of the uncommitted
changes that were previously performed just as I already do when using
cached updates.

In short, I would add in a new cached updates status of cuPosted and keep
track of them for refresh purposes.

Regards,
Jason