Thanks for the response, but I'm still rather unclear:
>You obviously can't control the transaction scope outside of your
>web application. The problem would be any attempt to enlist in a
>wider scope than you are allowed to use. This happens automatically
>in some cases.
I don't understand what you mean about the transaction scope being outside of my application. If I look at the BLL of the TBH (Order object), I had thought the scope began and ended in the BLL, with a trickling down to the DAL so that commands could be properly transactioned. Could we not specify the transaction scope as root? Would that prevent an attempt to enlist in an ambient scope I don't have access to?
Do all databases work with TransactionScope? I'm really jazzed about the concept, it would make my code much more elegant.