conn.Errors.Cou nt or err.Number for Transactions?

[Colin Steadman]

What is the best way to control is a transaction? I've done a little test and both of the examples below seem to do the job, but I was wondering which is the better method, this:

If err.number <> 0 Then
conn.RollbackTr ans
Else
conn.CommitTran s
End If

Or this:

If conn.Errors.Cou nt <> 0 Then
conn.RollbackTr ans
Else
conn.CommitTran s
End If

TIA,

Colin

[Ray at]

I'd probably do both, reason being:

a=10
b=0

conn.execute "some sql statement"
conn.execute "update something set this = " & Cint(a/b)

That wouldn't yield a conn.error, but if would give an Err.Number <> 0.
If Err.Number <> 0 Or Conn.Errors.Cou nt <> 0 Then
conn.RollbackTr ans
End If

But, better yet, handle this at the database level! Are you using SQL
Server? If so, use stored procedures with error checking and transactions
and things.

Ray at work
"Colin Steadman" <ms**@N0Tpart0F emailADDRESScol insteadman.com> wrote in
message news:E1******** *************** ***********@mic rosoft.com...

What is the best way to control is a transaction? I've done a little test and both of the examples below seem to do the job, but I was wondering which
is the better method, this:
If err.number <> 0 Then
conn.RollbackTr ans
Else
conn.CommitTran s
End If

Or this:

If conn.Errors.Cou nt <> 0 Then
conn.RollbackTr ans
Else
conn.CommitTran s
End If

TIA,

Colin

[Colin Steadman]

----- Ray at <%=sLocation% > [MVP] wrote: ----

I'd probably do both, reason being

a=1
b=

conn.execute "some sql statement
conn.execute "update something set this = " & Cint(a/b

That wouldn't yield a conn.error, but if would give an Err.Number <> 0
I see what you mean
If Err.Number <> 0 Or Conn.Errors.Cou nt <> 0 The
conn.RollbackTr an
End I

Right the code above it is then
But, better yet, handle this at the database level! Are you using SQ
Server? If so, use stored procedures with error checking and transaction
and things
No, its an Oracle database I'm connecting too. I dont think I like the idea of using stored procedures anyway. I dont know what it is, but there is something about databases and SQL,that really screws me up, I just cant get my head around it! To me they are like a rubix cube puzzle, I can move the pieces around alright, but I never quite get what I want. I think I'm missing some vital insight that'll make it all slide into place. I feel much more comfortable with ASP so I'll stick with that

Thank you for the advice Ray

Coli