 | ||
| 01000 | General warning | Driver-specific informational message. (Function returns SQL_SUCCESS_WITH_INFO.) |
| 01006 | Privilege not revoked | The prepared statement associated with the hstmt was REVOKE and the user did not have the specified privilege. (Function returns SQL_SUCCESS_WITH_INFO.) |
| 01006 | Privilege not revoked | The prepared statement associated with the hstmt was REVOKE and the user did not have the specified privilege. (Function returns SQL_SUCCESS_WITH_INFO.) |
| 07001 | Wrong number of parameters | The number of parameters specified in SQLSetParam was less than the number of parameters in the prepared statement associated with the hstmt. |
| 07006 | Restricted data type attribute violation | The data value could not be converted to the data type specified by fCType in SQLBindCol. |
| 08003 | Connection not open | The connection specified by the hdbc argument was not open. The conection process must be completed successfully (and the connecton must be open) for the driver to allocate and hstmt. |
| 08004 | Data source rejected establishment of connection | The data source rejected the establishment of a connection for implementation defined reasons. |
| 08S01 | Communication link failure | The communication link between the driver and the data source to which the driver was connected failed before the function completed processing. |
| 21S01 | Insert value list does not match column list | The argument szSqlStr contained an INSERT statement and the number of values to be inserted did not match the degree of the derived table. |
| 21S02 | Degree of derived table does not match column list | The argument szSqlStr contained a CREATE VIEW statement and the number of names specified is not the same degree as the derived table defined by the query specification. |
| 22001 | String data right truncation | The prepared statement associated with the hstmt contained a character parameter and the parameter value exceeded the maximum length of the associated table column. |
| 22003 | Numeric value out of range | The prepared statement associated with the hstmt contained a numeric parameter and the parameter value caused the whole part of the number to be truncated when assigned to the associated table column. |
| 22005 | Error in assignment | The prepared statement associated with the hstmt contained a parameter and the value was incompatible with the data type of the associated table column. |
| 22008 | Datetime field overflow | The prepared statement associated with the hstmt contained a date, time, or timestamp parameter or literal and the value was, respectively, an invalid date, time, or timestamp. |
| 22012 | Division by zero | The prepared statement associated with the hstmt contained an arithmetic expression which caused division by zero. |
| 22026 | String data, length mismatch | The data sent for a parameter was less than the length of data required. Typically, returned for SQL_LONGVARCHAR or SQL_LONGVARBINARY |
| 23000 | Integrity constraint violation | The prepared statement associated with the hstmt contained a parameter. The parameter value was NULL for a column defined as NOT NULL in the associated table column, a duplicate value was supplied for a column constrained to contain only unique values, or some other integrity constraint was violated. |
| 24000 | Invalid cursor state | Results were pending on the hstmt from a previous SELECT statement or a cursor associated with the hstmt had not been closed. |
| Invalid authorization specification | The value specified for the argument szUID or the value specified for the argument szAuthStr violated restrictions defined by the data source. | |
| 34000 | Invalid cursor name | The argument szSqlStr contained a dynamic positioned DELETE or a dynamic positioned UPDATE and the cursor referenced by the statment being prepared was not open. |
| 37000 | Syntax error or access violation | The argument szSqlStr contained an SQL statement that was not preparable or contained a syntax error. |
| 40001 | Serialization failure | The transaction to which the prepared statement associated with the hstmt belonged was terminated to prevent deadlock. |
| 42000 | Syntax error or access violation | The user did not have permission to execute the prepared statement associated with the hstmt. |
| 70100 | Operation aborted | The data source was unable to process the cancel request. |
| IM001 | Driver does not support this function | The driver associated with the hstmt does not support the function. |
| IM002 | Data source not found and no default driver specified | The data source name specified in the argument szDSN was not found in the ODBC initialization file nor was there a default driver specification. This message may also indicate that the ODBC initialization file could not be found. |
| IM003 | Driver specified by data source could not be loaded | The driver specified in the data source specification associated with the data source name in the ODBC initialization file was not found or could not be loaded for some other reason. |
| IM004 | Driver's SQLAllocEnv failed. | During SQLConnect, the Driver Manager called the driver's SQLAllocEnv function and the driver returned an error. |
| IM005 | Driver's SQLAllocConnect failed. | During SQLConnect, the Driver Manager called the driver's SQLAllocConnect function and the driver returned an error. |
| IM006 | Driver's SQLSetConnectOption failed. | During SQLConnect, the Driver Manager called the driver's SQLSetConnectOption function and the driver returned an error. |
| IM009 | Unable to load translation DLL | The driver was unable to load the translation DLL that was specified for the data source. |
| S0001 | Base table or view already exists | The argument szSqlStr contained a CREATE TABLE or CREATE VIEW statement and the table name or view name specified already exists. |
| S0002 | Table or view not found | The argument szSqlStr contained a DROP TABLE or DROP VIEW statement
and the specified table name or view name did not exist.
The argument szSqlStr contained an ALTER TABLE statement and the specified table name or view name did not exist. The argument szSqlStr contained a CREATE VIEW statement and a table name or view name defined by the query specification did not exist. The argument szSqlStr contained a CREATE INDEX statement and the specified table name did not exist. The argument szSqlStr contained a GRANT or REVOKE statement and the specified table name or view name did not exist. The argument szSqlStr contained a SELECT statement and a specified table name or view name did not exist. The argument szSqlStr contained a DELETE, INSERT, or UPDATE statement and the specified table name did not exist. |
| S0011 | Index already exists | The argument szSqlStr contained a CREATE INDEX statement and the specified index name already existed. |
| S0012 | Index not found | The argument szSqlStr contained a DROP INDEX statement and the specified index name did not exist. |
| S0021 | Column already exists | The argument szSqlStr contained an ALTER TABLE statement and the column specified in the ADD clause is not unique or identifies and existing column in the base table. |
| S0022 | Column not found | The argument szSqlStr contained a CREATE INDEX statement
and one or more of the column names specified in the column list did not exist
The argument szSqlStr contained a GRANT or REVOKE statement and a specified column name did not exist. The argument szSqlStr contained a SELECT, DELETE, INSERT, or UPDATE statement and a specified column name did not exist.. |
| S1000 | General error | An error occurred for which there was no specific SQLSTATE and for which no implementation specific SQLSTATE was defined. The error message returned by SQLError in the argument szErrorMsg describes the error and its cause. |
| S1001 | Memory allocation failure | The driver was unable to allocate memory required to support execution or completion of the function. |
| S1002 | Invalid column number | The value specified for the argument icol was 0, or the value exceeded the maximum number of columns supported by the data source. |
| S1003 | Program type out of range. | The rgument fCType was not a valid data type or SQL_C_DEFAULT. |
| S1008 | Operation canceled | Asynchronous processing was enabled for the hstmt. The function was called and before it completed execution, SQLCancel was called on the hstmt. Then the function was called again on the hstmt. |
| S1009 | Invalid argument value | The argument phdbc was a null pointer. |
| S1010 | Function sequence error | The specified hstmt was not in a prepared state.
SQLExecute was called without first calling SQLPrepare.
An asynchronously executing function (not this one) was called for the hstmt and was still executing when this function was called. |
| S1015 | No cursor name available | There was no open cursor on the hstmt and no
cursor name ahd been set with SQLSetCursorName.
The statement associated with the hstmt does not support the use of a cursor. For example, the CREATE TABLE statement. |
| S1090 | Invalid string or buffer length | A parameter value, set with SQLSetParam, was a null pointer and
the parameter length value was neither 0, SQL_NULL_DATA, or SQL_NULL_DATA.
A parameter value, set with SQLSetParam, was not a null pointer and the parameter length value was less than 0, but not equal to SQL_NTS, SQL_NULL_DATA, or SQL_DATA_AT_EXEC. |
| S1092 | Option type out of range | The value specified for the argument fOption was not SQL_CLOSE, SQL_DROP, SQL_UNBIND, or SQL_RESET_PARAMS |
| S1C00 | Driver not capable | The driver does not support the data type specified in the argument fCType. |
| S1T00 | Timeout expired | The timeout period expired before the data source returned the result set. The timeout period is set through SQLS |
Home