Trapping Informix Stored Procedure Exceptions

I have a VB program written to go against an Informix 7 DB Stored Procedure which I force to raise an exception. Using DAO, I get an error raised on the client. Using ADO, I don't get an error raised, but get a valid recordset returned with no data. Of course getting the error raised is the right thing to do. Can anyone tell me why ADO isn't raising the error. This will become a major issue if we decide to use ADO for our project (which we are intending). To be complete, I am using the InterSolv 3.10 client drivers and ADO 2.0 under VB6. Thanks, Paul Yurga pyurga@lucent.com