DisableCommit vs SetAbort

Can anyone tell me what the practical difference between the Root object in
a transaction calling DisableCommit and SetAbort on failure / an error
raised by one or more Secondary objects?

Basically, design-wise, I would like to have all Secondary objects call
DisableCommit on failure / error; and all Root objects call SetAbort on
handling such a failure / error. Can anyone supply a reason not to?


Many thanks,

James Brophy

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.