Thanks, all. This resolved the problem:-) Ilya
-----Original Message----- From: Jeff Urlwin [mailto:jurlwin@;bellatlantic.net] Sent: Wednesday, October 30, 2002 5:43 PM To: Sterin, Ilya (I.); [EMAIL PROTECTED] Subject: RE: :ODBC SQL Server problem > > > Using the latest DBI and DBD::ODBC to connect to SQL Server I'm > getting this error... > > Connection is busy with results for another hstmt > (SQL-S1000)(DBD: st_execute/SQLExecute err=-1) > > This happens when I use the same database handle to execute two > different statements. When I open two different connections, > this problem does not exist. It must be some sort of a DBD::ODBC > or ODBC config, since using OLEDB, this also is not an issue. Yes, this is a known issue and one caused by the driver itself. Sybase also seems to have (or used to have) this limitation. There is a "workaround" by setting odbc_SQL_ROWSET_SIZE (please see docs in ODBC.pm), but I've heard from Martin Evans (someone who has provided valuable and accurate insights in the past) that there are cases where this can cause the SERVER to hang/crash... Regards, Jeff
