-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You have two active statement handles and SQL Server does not support multiple active statements with the standard cursor. i.e. you are attempting to issue a query under a connection whilst you still have another active query (under the same connection) you have not finished retrieving yet. The easiest way around this in DBD::ODBC is to open multiple connections.
Martin - -- Martin J. Evans Easysoft Ltd, UK Development On 30-Oct-2002 [EMAIL PROTECTED] wrote: > 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9wO9ajLvsvprkFrMRApKVAJ9cT86eTl7d5lMrtAqUzMVglVu5kwCeJZzI Y/NGZBogI3OxVj0POQiQq10= =GiS2 -----END PGP SIGNATURE-----
