in reply to Re^3: DBI Invalid Cursor State when PRINT statements are embedded in SQL
in thread DBI Invalid Cursor State when PRINT statements are embedded in SQL

This was helpful... but any idea how can I capture both the SQL_SUCCESS_WITH_INFO __AND__ the results of the select? I see $dbh->errstr has MicrosoftODBC SQL Server DriverSQL Server...begin(SQL-01000) when the PRINT statement is run all alone, but get the cursor error when it is run with the select... arrgh...
  • Comment on Re^4: DBI Invalid Cursor State when PRINT statements are embedded in SQL

Replies are listed 'Best First'.
Re^5: DBI Invalid Cursor State when PRINT statements are embedded in SQL
by 18th_bronzeman (Novice) on Sep 21, 2007 at 23:00 UTC
    Hello guys.

    I researched this one and found a site with a solution that works. It is pretty helpful, but seems a little hard to use the statements for what they were meant for, logically organizing the output. I am still working to trap the PRINT statements in a meaningful way so that they appear in the data (array or output file) the way that the DBA meant them to.

    If anyone reading this is an error trapping guru it would be nice to know how to trap these statements in a meaningful way. I don't really understand how that second while loop does what it does. For now, I can only seem to get them to appear on the console.

    Here is the link to the page that breaks it all down:

    http://www.easysoft.com/developer/languages/perl/sql_server_unix_tutorial.html#print_statement_status_messages
[reply]

In Section Seekers of Perl Wisdom