ODBC returning -1 instead of 1 after record insert on some PCs

While we’re on the topic of ODBC this morning.

I have an interesting one.

A .Net desktop app that runs on multiple PCs is inserting new records.

The inserts always work just fine so there’s no issue there.

But on some of the machines we’re getting a -1 instead of 1 for the returned value after the ExecuteNonQuery operation to insert records. (The return code stands for records affected/modified.)

Reading the ODBC docs say that all operations other than INSERT, UPDATE, DELETE can return a -1 for success, but the CRUD options should always return records affected/modified.

Only thing I can think so far is the PCs possibly have different versions of the IBM Access ODBC Driver on them and that older versions of the ODBC driver didn’t send back records affected correctly.

Any other thoughts or ideas are appreciated.


Regards,
Richard Schoen
Web: http://www.richardschoen.net<http://www.richardschoen.net/>
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>