RE: DBD::ODBC problem.

A known issue that affected SQLServer 6.5 (and I'm guessing 7.0) is that if you open a cursor using a prepare/execute and start reading through it, if you perform a commit or rollback and then try to continue reading from the cursor (perform another fetchrow) you will get the error you describe. I.E. The cursor is closed by the commit/rollback.
I don't know if this is your problem but it's worth checking.

Comment on RE: DBD::ODBC problem.

Replies are listed 'Best First'.
RE: RE: DBD::ODBC problem. by Corion (Patriarch) on Aug 09, 2000 at 13:36 UTC
I have no MS SQL Server 7.0 available to test this, but the MS SQL Server 7.0 is a complete rewrite, as Microsoft does not use the Sybase codebase anymore. So I'd assume a lot of differences between 6.5 and 7.0.	[reply]
RE: RE: RE: DBD::ODBC problem. by PsychoSpunk (Hermit) on Aug 09, 2000 at 21:05 UTC
There is a service patch available that allows backwards compatibility (read allows old Sybase connection libs to be used). It's been mentioned here before, I believe, and it's recommended by Michael Peppler in order to work with DBD::Sybase. I'm waiting for his reply on the dbi-users mailing list about my other problems with that. Looks like I found a project to join. :) ALL HAIL BRAK!!!	[reply]