I have an app consisting of C and VB. I now need that code to use DB2 via
ODBC (currently runs against all other major brands of db). The problem is,
unlike every other database DB2 returns a warning if a SQL statement does
not delete or modify any rows. For all other vendors the statement is
simply successful.
For the short term we can generate a bunch of DB2 specific code to check for
SQL02000. Crude. I can't be the only person dealing with this. How do
others handle this? Is there a way to make SQL02000 appear as successful?
Scott