I may be missing something, but saving objects with a parent child relationship under a transaction does seem to work properly. Attached is a simple example. It consists of one parent object with two child objects. When the three objects are saved outside of a transaction, everything works as expected. However when they are saved under a transaction, the framework saves the parent three times.

-Larry

Yeah, it will do that... the business objects still return IsDirty = True until TransactionCommitt is called (just in case you roll back the transaction).  So, when the child checks its parent, it will still be dirty and will think it needs to save again.  Hrm... I'll have to think about this one; might take me a little while.  I do have a collection of the DataTables that have participated in the transaction already, so I can probably test on that.

Tracking objects that have been saved but not comitted without using the IsDirty property would also fix the issue I mentioned in the following post.

http://forum.strataframe.net/Topic9625-10-1.aspx?Highlight=transaction

Yes, it would... I think that thread was overlooked... because by the time I saw it, it had degraded to talking about blowing up cement trucks and such   I'll let you know when I have a fix.

I wouldn't go so far as to say degraded... you got to love TV shows where they blow up things

anything new on this???

Jason Seidell

Programmer/Analyst

Infinedi