>>Connection has errors collection and error object. Sample VB < bg > code from ADO210.chm :
>> On Error GoTo ErrorHandler
>The COM will not build with an ON ERROR. There is a GETCOMRETURNERROR(), but I don't think it bites until after the interupt. The RecordSet.Open interupts when the command/stored procedure request is no good. The ADODC 'container' has an error method that intercepts SQL errors, then allows COM to set it's own return flags and .NULL. the record set. For ADODB, the GETCOMRETURNERROR advertises to cancel COM processes, and return to the client, but how to do, how to do? I am going to just set an ERROR method for each object in the com and see if any of them get hit.
>
>Thanks for the code.
>Terry

Terry,
If ADODC has it why not use it. In the thread I mentioned it was reported to fail on other site but I have many working samples using it (I never tried it with COM though).
I think the key is your signature :)
Cetin