Mike,
thanks and whew! I was/am aware of those issues - just wanted to make sure I wasn't missing something. All my SQL calls - both SPT and my tableupdate/revert wrappers are handled through one mid-tier class that deals with the rollback/commit.
I do have a way to set automatic on if needed - but that is exception - not rule - in my framework.
Thanks!
>Ken,
>
>Don't mis-read what I wrote. I'm not saying that setting the connection to implement manual transactions is wrong. I was only filling in the backgroud with what I know.
>
>The only place that you might run into issues is if you forget to commit or rollback the transaction. The other thing to remember is that a SELECT query will also start a transaction. You can see this with the following:
>
>set implicit_transactions on
>select * from authors
>select @@trancount
>
>run this in the QA. Don't forget to issues a ROLLBACK to kill the transaction.
>
>-Mike
Ken B. Matson
GCom2 Solutions