Not sure to understand your question, but.. :)
When I have master-detail tables, I put all datasets inside one transaction. This way I can commit or roll back all data (master and detail), but not detail only or master only (that could be too difficoult to understand by users).
So I've build a specialized version of IB_UpdateBar, that I call IB_UpdateWorkBar that if no transaction is assigned, works like the normal IB_UpdateBar, but if a transaction is assigned, manages post and cancel affecting the whole transaction and associated datasets (i.e. Post does a PostAll, then a Commit...).
It also adds two events that I need in my base data entry forms.
If you are interested in it, I can put it in the file section of the list, but beware that, even if very simple in use, it has not finisched at top level of details, since it's, at this time, for my own use. I think that this would be an interesting additional component for IBO distribution, but I would need to find the time to improve it a little bit, make a demo app, use cool button glyps, translate comments into english, write some line of help, and sent it to Jason ;)
regards
Marco Menardi

--- In IBObjects@y..., Raymond Kennington <progsol@c...> wrote:
> Supposing, then, that there is a master table and a detail table and I want either the
> master record and all its detail records either all posted or none posted in a single
> transactional unit, is it possible to alter the Post behaviour of the Post button in the
> UpdateBar connected to the master table to issue a PostRetain rather than a Post?
>
> What is the standard way of using IBObjects to solve the single-unit transaction of a
> master record and all its children?
> --
> Raymond Kennington
> Programming Solutions
> W2W Team B