Would it be possible for you to create a new dataset component able to work with two different transactions, one for browsing, other for "editing"?
Browsing would use RC-RO transaction (that can be left open for years without compromising FB performance), while posting would use separated short-time transaction with desired isolation. This should be done in a way that when I have several datasets posting related changes (ie: master detail) with CachedUpdates, all of the involved datasets would use the same "post" transaction.
PS: It should be available for TDataset comps too.
Excellent suggestion. This should be in first priority and no priority 5.