|laziness, impatience, and hubris|
DBI Invalid Cursor State when PRINT statements are embedded in SQLby JamesNC (Chaplain)
|on Oct 18, 2004 at 17:49 UTC||Need Help??|
JamesNC has asked for the wisdom of the Perl Monks concerning the following question:
Win32 AS-5.8.0 Multithread build 806 DBI(1.43)DBD::ODBC(1.07) MSSQL Server I get a invalid cursor state when I run any SQL with a PRINT statement at the beginning of any SQL statement.
If you move the PRINT statement AFTER the select statement, you don't get the error, but you also don't see the output of the print.
Does anyone know how to capture the output of the PRINT Statements? They seem to print on command line tools like ISQL and other programs like Embarccadaro. Is my SQL in bad form here or is this a problem I am not working correctly in DBI?
Thanks in advance!