| title |
SQL_NO_DATA |
| description |
SQL_NO_DATA |
| author |
David-Engel |
| ms.author |
davidengel |
| ms.date |
01/19/2017 |
| ms.service |
sql |
| ms.subservice |
connectivity |
| ms.topic |
concept-article |
| helpviewer_keywords |
SQL_NO_DATA [ODBC] |
application upgrades [ODBC], SQL_NO_DATA |
backward compatibility [ODBC], SQL_NO_DATA |
compatibility [ODBC], SQL_NO_DATA |
upgrading applications [ODBC], SQL_NO_DATA |
|
When an ODBC 3.x application calls SQLExecDirect, SQLExecute, or SQLParamData in an ODBC 2.x driver to execute a searched update or delete statement that does not affect any rows at the data source, the driver should return SQL_SUCCESS, not SQL_NO_DATA. When an ODBC 2.x or ODBC 3.x application working with an ODBC 3.x driver calls SQLExecDirect, SQLExecute, or SQLParamData with the same result, the ODBC 3.x driver should return SQL_NO_DATA.