On Wed, 2002-10-30 at 14:43, Jeff Urlwin wrote: > > > > > > 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.
Yes, Sybase does have the same limitation (understandable, they share a common base architecture). DBD::Sybase works around this by opening additional connections "under the covers". Not the best of solutions, but at least existing scripts that have multiple $sth open at the same time will have a chance of working. Michael -- Michael Peppler / [EMAIL PROTECTED] / http://www.mbay.net/~mpeppler [EMAIL PROTECTED] / ZetaTools, Inc / http://www.zetatools.com ZetaTools: Call perl functions as Sybase stored procedures!
signature.asc
Description: This is a digitally signed message part
