| title |
Calling SQLGetDiagField |
| description |
Calling SQLGetDiagField |
| author |
David-Engel |
| ms.author |
davidengel |
| ms.date |
01/19/2017 |
| ms.service |
sql |
| ms.subservice |
connectivity |
| ms.topic |
concept-article |
| helpviewer_keywords |
application upgrades [ODBC], SQLGetDiagField |
backward compatibility [ODBC], SqlGetDiagField |
upgrading applications [ODBC], SQLGetDiagField |
SQLGetDiagField function [ODBC], calling |
compatibility [ODBC], SQLGetDiagField |
|
When an ODBC 3.x application calls SQLGetDiagField in an ODBC 2.x driver, the driver will return SQL_SUCCESS and the appropriate information in *DiagInfoPtr if the DiagIdentifier argument is SQL_DIAG_CLASS_ORIGIN, SQL_DIAG_CLASS_SUBCLASS_ORIGIN, SQL_DIAG_CONNECTION_NAME, SQL_DIAG_MESSAGE_TEXT, SQL_DIAG_NATIVE, SQL_DIAG_NUMBER, SQL_DIAG_RETURNCODE, SQL_DIAG_SERVER_NAME, or SQL_DIAG_SQLSTATE. All other diagnostic fields will return SQL_ERROR.