Each function in ODBC returns a code, known as its return code, which indicates the
overall success or failure of the function. Program logic is generally based on return
codes.
Function failed. The application calls SQLGetDiagRec or SQLGetDiagField to
retrieve additional information. The contents of any output arguments to the
function are undefined.
Function failed due to an invalid environment, connection, statement, or
descriptor handle. This indicates a programming error. No additional information
is available from SQLGetDiagRec or SQLGetDiagField. This code is returned only
when the handle is a null pointer or is the wrong type, such as when a statement
handle is passed for an argument that requires a connection handle.
More data is needed, such as when parameter data is sent at execution time or
additional connection information is required. The application calls SQLGetDiagRec
or SQLGetDiagField to retrieve additional information, if any.
No more data was available. The application calls SQLGetDiagRec or SQLGetDiagField
to retrieve additional information. One or more driver-defined status records in
class 02xxx may be returned. Note: In ODBC 2.x, this return code was named
SQL_NO_DATA_FOUND.
A function that was started asynchronously is still executing. The application
calls SQLGetDiagRec or SQLGetDiagField to retrieve additional information, if any.
Function completed successfully, possibly with a nonfatal error (warning). The
application calls SQLGetDiagRec or SQLGetDiagField to retrieve additional
information.