Re: What happens to non-commited transaction
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Thu, 30 Jun 2005 14:04:26 -0700
When a connection (which holds the transaction state) is closed by the
client end, the server rolls back any open transactions automatically.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Larry" <bliff@xxxxxxxxxx> wrote in message
news:u$2c9XZfFHA.3916@xxxxxxxxxxxxxxxxxxxxxxx
> In VB 6, using ADO, SQL Server 2000
>
> In my VB program I use the connection object (abc)
> to begin a transaction.
>
> abc.BeginTrans
>
> I then, in my VB App, using ADO, execute multiple stored procedures
> inserting records into temp tables ##Meetings,
> reading them, and then finnaly executing (from my VB app
> using ADO) as stored procedure that inserts records
> into a non-temp table.
>
> I then have a abc.CommitTrans
>
> What if my VB program crashes before the
> committrans is executed, I assume that the transaction
> is rolled back, even though no explicit rollback
> is issued, because my VB program has crashed.
>
> Thank You for your help,
>
> Laurence Nuttall
> Programmer Analyst III
> UCLA - Division of Continuing Education
.
- References:
- What happens to non-commited transaction
- From: Larry
- What happens to non-commited transaction
- Prev by Date: Re: HOW DO I EDIT A RECORD IN ADO
- Next by Date: Re: Retrieving warnings from a stored procedure in ADO (VB6)
- Previous by thread: What happens to non-commited transaction
- Next by thread: recordset get single row shortcut?
- Index(es):
Relevant Pages
|
|