Knowledge Base  
PRB: ADO Errors Collection Does Not Contain User-Defined Error Messages
SYMPTOMS
Executing a SQL Server stored procedure (SP) by using ActiveX Data Objects 
(ADO) does not populate the ADO Errors collection of the Connection object with 
user-defined errors that are raised in the SP. This behavior only occurs when using 
the OLE DB Provider for SQL Server (SQLOLEDB) to establish an ADO connection to 
the SQL Server database. 

CAUSE
This problem is specific to the SQLOLEDB. It only occurs when the NOCOUNT SQL 
Server option has been turned OFF, which is the default setting. 

RESOLUTION
Either of the following resolutions may be used to address this issue: 

Turn on the SQL Server NOCOUNT option by using the SET statement before 
executing the stored procedure by using an ADO connection or command. This 
adds the user-defined error messages raised in the SP to the ADO Connection 
object's Errors collection.
-or-
Use the OLE DB Provider for ODBC (MSDASQL) to open the ADO connection to SQL 
Server. The MSDASQL Provider establishes the connection to the specified SQL 
Server by using the SQL Server ODBC driver. The ADO Errors collection is 
populated with user-defined errors raised in the SP without having to turn on the 
NOCOUNT option when executed by using an ADO Connection opened with the 
MSDASQL Provider.