While scouting around this group, I've stumbled upon this ASP script
which deals with rolling back transactions -
'-- Error Handler
if oConn.Errors.Co unt > 0 then
oConn.RollbackT rans
Response.Write( "FAIL")
Response.End
Response.write( err.description )
end if
Which has given me pause to wonder if what I am doing is correct. I'm
basing my rollback on the err.number not being 0 (sample code below).
Is this ok, or should I be using the conn.errors.cou nt property
instead?
TIA,
Colin
If Not UpdateDealerPeo pleInfoPending Then
conn.RollbackTr ans
response.redire ct("msg_employm ent_status_upda te.asp?error=2" )
End If
Function UpdateDealerAct ionsSummited()
On Error Resume Next
sql = "random sql update statement"
conn.execute sql, , &H00000080
Set sql = Nothing
'Errors?
If err.number <> 0 Then
UpdateDealerAct ionsSummited = False
Else
UpdateDealerAct ionsSummited = True
End If
End Function
which deals with rolling back transactions -
'-- Error Handler
if oConn.Errors.Co unt > 0 then
oConn.RollbackT rans
Response.Write( "FAIL")
Response.End
Response.write( err.description )
end if
Which has given me pause to wonder if what I am doing is correct. I'm
basing my rollback on the err.number not being 0 (sample code below).
Is this ok, or should I be using the conn.errors.cou nt property
instead?
TIA,
Colin
If Not UpdateDealerPeo pleInfoPending Then
conn.RollbackTr ans
response.redire ct("msg_employm ent_status_upda te.asp?error=2" )
End If
Function UpdateDealerAct ionsSummited()
On Error Resume Next
sql = "random sql update statement"
conn.execute sql, , &H00000080
Set sql = Nothing
'Errors?
If err.number <> 0 Then
UpdateDealerAct ionsSummited = False
Else
UpdateDealerAct ionsSummited = True
End If
End Function
Comment