This content has been marked as final. Show 3 replies
Are you sure it's returning 'S1000'? That doesn't appear to be a valid ODBC 3.0 SQLSTATE code. The SQLSTATE codes changed between ODBC 2.0 & 3.0, so if your app is announcing itself as ODBC 2.0 compliant, you'll get back ODBC 2.0 error codes. 'S1000' may be the correct ODBC 2.0 translation of the '08S01' ODBC 3.0 SQLSTATE.
I'm positive about the 'S1000'.
I saw that some ODBC functions did produce
the SQLSTATE '08S01', whereas other
functions produced SQLSTATE 'S1000'. This
is an ODBC 2.0 compliant state meaning
something like 'general error'.
So I still don't know in some cases that
my connection was lost. Does anybody know
how to solve my problem ??
-- Andri W.
Which functions are returning the correct error code, and which are returning the incorrect code?
Is it possible that one function returns the correct code, then the subsequent functions return the general error 'S1000'? This would seem to make sense to me, since the driver may only notice the dropped connection once, when it's actually lost. After that, anything you do on the connection would fail in a nondescript manner.