> -----Original Message-----
> SQL Server supports it, and after you do a commit or rollback, it
> automatically starts you with a new (implicit) transaction.
>
> So I still don't see a problem with commits in SP.

Implicit = lack of control (imo).

TBH I would like to see stored procs support transactions as well, but only
so far as an SP can create and subsequently rollback or commit the
transaction *IT* creates. The SP should have absolutely no bearing on the
client application's transaction.

Rgds

Si Carter
http://www.fbtalk.net/
http://www.tectsoft.net/