Original message: By: Synametrics support engineer
Lars,
This is definitely a bug in WinSQL and it occurs when the ODBC driver is not able to return the number of rows affected. In that case, a -1 is returned. WinSQL tries to cast this -1 to an unsigned integer, resulting in Integer.MAX_VALUE.
We will fix this in the next build. However, you still won't see the actual number of rows affected since the back-end does not return this value. Instead, you will see something like "This command did not return data, and it did not return any rows"
Imran
