Paul,

As I understand it, ADO does not trap or handle errors; rather, it records the occasions when errors occur. So YES, you would check the Errors collection after the error has been generated; but NO, you wouldn't need to keep the error from popping up on the screen because it's up to the application to do that, not the ADO connection object.

I've always used the "check for null value" route until I determined that I did not have a connection, -then- checked the Errors collection to figure out WHAT the error was and/or WHY there was a problem. Some developers don't want the extra step of checking for the null, so they just look for the existence of an error instead. Two different approaches to the same result, IMHO.

And you're NOT ignorant -- ADO is a new technology to most of us. I've been very fortunate to have the opportunity to use it quite a bit lately. It's taken some "getting used to" for many, including yours truly (g)...

>Pardon my ignorance (I'm fairly new at this), but wouldn't I have to check the Errors collection after the error has already been generated? And if so, then how do I keep the error from popping up on the screen?