Anyone can point me in the right direction regarding the below error. 
Using the latest DBI and DBD::ODBC, when one connection is open and two
different statement handles are prepared and executed, the second
statement handle throws this exception...

Connection is busy with results for another hstmt (SQL-S1000)(DBD:
st_execute/SQLExecute err=-1)

I can't figure out what it can be.  This script works just fine using
OLEDB, but not with DBD::ODBC.

Thanks.

Ilya

Reply via email to