Q: Raising Exceptions using Informix Stored Procedures, MTS, NT4.0, VB6 Webclasses

Hi All, I was recently added to a project using the above technologies to implement a multitier intranet application. The problem I have found is that errors raised within the stored procedures do not get propagated back to the VB procedure. Instead, the VB client hangs, consuming the CPU. Note that this occurs only with stored procedures, generating an error in SQL produces the appropriate message. I think that the guilty party is the ODBC driver, which I am told is a beta. Software we are using: Informix 7.21 Microsoft NT4.0 VB6 Stored Procedures (Called by generating the sql Ex: "execute procedure procname (param1, param2);" The driver we are using is Informix 2.80.79999 (I am told this is a beta) The most recent driver we received is Informix 2.80.50000. This one was tested and was not useable in our environment. An intersolv driver (version unspecified but I can find out if necessary was also tried unsuccessfully). So, can anyone shed any light on this? Specifically: 1. Is there a more recent Informix driver that supports MTS and Informix? By Informix or another vendor? 2. Has anyone else seen this problem? Any useful workarounds? The only thing I have come up with is to trap the errors in the procedures and return a null recordset, but that is pretty hokey. If any more info is needed to answer lemme know. Regards and TIA, Kelly