S
saiidcd@gmail.com
Guest
Thanks Both James and Thomas for the quick answers, I am aware of the potential for this leading to a large transaction scope, however the main point I am trying to get to the bottom of is, can I group transactions together so I can roll back if one fails even when the call is from a .Net code into progress? If it makes it easier, you can forget about the commit part so the code looks more like: 1.Start Transaction TA: 2. do some work 3.Create Customer 4.do some more work some of it based on created customer 5.Create Order 6.Do some more work based on customer and/or order 7.Create OrderLine 8.Do some final work. 9. Commit transaction TA If my code fails or decides to roll back at lines 4,6 or 8 would I be able to roll back the progress transaction? The above code would be in a Business Logic layer that is calling a Data Access layer. The data access layer can be a 4GL based layer.
Continue reading...
Continue reading...