>What Sam (I believe) is referring to is a transaction situation where you would never save one record by itself as in the double entry method of accounting world dictates debits equal credits, therefore you would need at least two records saved or none. To facilitate this he would need a parent child relationship between two business objects via the framework and utilize database transactions.
>

I was thinking about what you said and I wonder why he can't just manage the transactions even on a single business object manually. If he sets the TransactionBegin on his business object and don't call the TransactionCommit until he has edited all the records would he not get the effect needed and have finer control over what he is wrapping in the transaction? I have not done this so do not know how the form level stuff gets handled but would be easy enough to figure out.
Tim