Re^3: DBI on windows problem

Nothing in that jumps out at me as wrong (on the Perl side) except that you don't set RaiseError, warnings, or strict. Perhaps adding those will give you some more information.

On the off-chance that there's a bug in your version of DBD::ODBC's rows(), you could see if the results are any different with just $rcount2 = $getinfo->execute() which should also return the rows affected for non-SELECT statements.

Comment on Re^3: DBI on windows problem

Replies are listed 'Best First'.
Re^4: DBI on windows problem by txtoolman (Initiate) on Nov 05, 2007 at 18:12 UTC
I used the code you suggested - no change. Then I defined a second $dbh (identical to the first one), and used the new $dbh with the delete statement. I got the numbers I was suppose to get. I'm very curious why this is needed for the delete line, but for the updates and insert lines, there are no problems. One other thing I was thinking: would using the Win32::ODBC module be more reliable?	[reply]