How does the classic asp connection.errors collection actually work?

Question

I am trying to confirm how the actual ADODB.Connection.Errors collection should actually work.

My interpretation at the moment is that the connection will hold all the errors for the all the procedures that have been executed on that connection.

So I should be able to say

on error resume next 

... code goes here ... 2 or more command objects execute procedures against the database on the same connection

if con.Errors <> 0 then 

  loop through all the Errors objects (1 for each procedure that would've been executed on the connection)

end if

However I have implemented that basic structure and I only get the one error description? So I am looking for someone to confirm that is the case. Does the Errors collection hold more than one error for more than one procedure? Or is if multiple errors occurred for one procedure?

I can't seem to find any documentation that would indicate exactly what would happen in this case.

Thanks,

score 2 · Accepted Answer · answered Jan 03 '12 at 23:06

from Errors Collection (ADO) - MSDN:

Any operation involving ADO objects can generate one or more provider errors. As each error occurs, one or more Error objects can be placed in the Errors collection of the Connection object. When another ADO operation generates an error, the Errors collection is cleared, and the new set of Error objects can be placed in the Errors collection.

So, to catch all errors, seems to be need to check the collection after each possible error.

Thanks, that's clear and concise. It also matches with what I've been seeing in my code ... Thanks — Kevin Donde, Jan 04 '12 at 14:40

How does the classic asp connection.errors collection actually work?

1 Answers1