Very Computer

Thanks

On Error Resume Next    'Enable error checking
rs.Update
If cn.Errors.Count <> 0 then
    'Do something
    cn.Errors.Clear
End If
On Error GoTo 0            'Turn off error checking

You use the On Error statement in those places where an error is
likely.
Or, you can wait til VB7 to use Try...Catch!

 - Tom

Quote:> Is there a way to tell ADO to NOT stop when an error occurs, but
allow
> me to check the error code collection to check the errors?  Eg. I do
> not wish to use a ON ERROR RESUME NEXT in my code, but tell ADO to
> continue when it has an error and allow me to check the error via.
> code.

> Thanks

If you use On Error Resume Next then you should check if an error as
occcured as often as possible
e.g.

    Dim rs as ADODB.Recordset

    rs.Open xx,yy,zz,blag, blah

    if Err.Number <> 0 then
        msgbox "An Error occured opening the recordset " & Err.Number & " "
& Err.Description
    endif

    rs.movefirst

    if Err.Number <> 0 then
    endif

On error Goto Handle
....ADO stuff

On error goto 0
Exit sub/func
Handle:
    msgbox Err.Description '<-------Handle error
   resume next
   exit sub/func
End sub/func

By the way, I was wondering why you didn't clear the error in your
example.

  - Tom

Quote:> Or:

> On error Goto Handle
> ....ADO stuff

> On error goto 0
> Exit sub/func
> Handle:
>     msgbox Err.Description '<-------Handle error
>    resume next
>    exit sub/func
> End sub/func

Quote:> I prefer to enable error trapping *only* when I suspect an error is
> possible. If the error occurs, handle it, clear the error and disable
> error trapping. If an error occurs somewhere that I didn't anticipate,
> the user will get a run time error message. I'll hear about it and
> have to fix it.

--

Thanks,
Carl Prothman
Microsoft Visual Basic MVP
http://www.able-consulting.com

Please reply in the newsgroup.  I am unable to respond to requests for
assistance via private e-mail.

All erroes whould be trapped even if its just to provide a more polite
message to the user that something has gone wrong tather that having the
weird message "Object x does not support method Y" etc.

It also allows you to gracefully exit the application by properly closing
resources in use such as open files or ado tables,
network connections, references to objects etc. etc. etc.