>
>Thank you very much. I have had very similar experience in working with biz object for two or more tables. And I thought I was missing some very basic concepts. And I also thought about creating some properties in the "primary" table BIZ object to "hook" BIZ objects for "child" or "secondary" tables. This way, my basic BIZ class can be used in a simple case and in some more complicated ones.

About the only thing I do for that is I have a "TransactionSave()" method on my bizobjs. You can pass in one or more bizobjs (and cursor names) and it will wrap all of them into a transaction and call the "Save" method on each of them. If any of them fail I rollback the transaction. Error messages get bubbled back up to the primary bizobj (whose TransactionSave you called).