ODBC (Level 2)

Installing SQL Server

ODBC (Level 2)

SQL Server 6.x	SQL Server 2000
SQL_ERROR was returned by SQLExecute, SQLExecDirect, or SQLParamData when extended stored procedures or batches met the following criteria: The first data-returning statement caused an error (either by a run-time error or a RAISERROR statement with severity greater than or equal to 11). There was data from any other statement, even a simple RETURN statement, after the error-causing statement. Due to the SQL_ERROR return code, the statement handle was available for use immediately.	SQL_SUCCESS_WITH_INFO is returned when an ODBC 3.x application uses the ODBC SQL Server 3.51-compliant driver included with this release (using SQLExecute, SQLExecDirect, or SQLParamData). Due to the SQL_SUCCESS_WITH_INFO return code, process the results for that statement handle before it is available for use. Expect different results as compared to earlier versions of SQL Server. Handle SQL_SUCCESS_WITH_INFO using SQLGetDiagRec, and then call SQLMoreResults to process the remaining results, as appropriate.

SQL Server 6.x

SQL Server 2000

SQL_ERROR was returned by SQLExecute, SQLExecDirect, or SQLParamData when extended stored procedures or batches met the following criteria:

The first data-returning statement caused an error (either by a run-time error or a RAISERROR statement with severity greater than or equal to 11).
There was data from any other statement, even a simple RETURN statement, after the error-causing statement.

Due to the SQL_ERROR return code, the statement handle was available for use immediately.

SQL_SUCCESS_WITH_INFO is returned when an ODBC 3.x application uses the ODBC SQL Server 3.51-compliant driver included with this release (using SQLExecute, SQLExecDirect, or SQLParamData).

Due to the SQL_SUCCESS_WITH_INFO return code, process the results for that statement handle before it is available for use.

Expect different results as compared to earlier versions of SQL Server. Handle SQL_SUCCESS_WITH_INFO using SQLGetDiagRec, and then call SQLMoreResults to process the remaining results, as appropriate.

previous page start next page