Posted by Erland Sommarskog on 07/01/05 00:35

Larry (Bliff@Bliff.com) writes:
> 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.

Yes.

If you want to verify - and this is a good exercise just try it. For
instance run the program from the VB debugger set a break point somewhere,
and then kill VB from the Task Manager. Now check that there is no data
which should not be there.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: Setting permissions on master.dbo.syslogins
• Prev in forum: Re: stupid SQL question on Where clause
• Thread view: Re: Transaction not commited rollback?

[Reply to this message]