Informix Error -50943
Cause and resolution
[Informix][Connectivity Class Library]Error occurred in ixSQLStmt::getNativeTypeName(). The column number may be out of range or the statement may not be prepared.
The statement might not be prepared yet. Try calling ixSQLStmt::prepare() before ixSQLStmt::getNativeTypeName(). Verify that the column number is in the range from 1 to the value returned by ixSQLStmt::numResultCols().
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-50943 fires as described in the archived official text: The statement might not be prepared yet. Try calling ixSQLStmt::prepare() before ixSQLStmt::getNativeTypeName(). Verify that the column number is in the range from 1 to the value returned by ixSQLStmt::numResultCols().
- [Informix][Connectivity Class Library]Error occurred in ixSQLStmt::getNativeTypeName(). The column number may be out of range or the statement may not be prepared, per the archived official text — the direct, named condition.
Solutions / Resolution
- Call
ixSQLConnect::SQLError()for the underlying ODBC error detail, per the archived official text, before trying to resolve this further. - Try a different ODBC driver, per the archived official text, if the error appears driver-specific.
- If the error recurs, note all circumstances and contact Technical Support, per the archived official text.
Examples
N/A
No specific triggering statement is documented beyond the archived official text's own description of this Connectivity Class Library (CCL) condition.
Diagnostic Checks
- Call
ixSQLConnect::SQLError()(or the equivalent for the class involved) to retrieve the underlying driver-level error detail, since the CCL-level message alone is not more specific than what's shown here.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -50943 in this set yet.
[Informix][Connectivity Class Library]Error occurred in ixSQLStmt::getNativeTypeName(). The column number may be out of range or the statement may not be prepared. — per the archived official text, retrieve the ODBC-level error detail via ixSQLConnect::SQLError() before escalating.