The following table lists the possible values which can be returned in the cmdhdr.rc field. Note that the function Fn’SQL’ErrMsg$() in the include module SQL:FNSQLERR.BSI provides an easy way to display the text associated with the numeric error codes.
Symbol |
Value |
Notes |
|---|---|---|
SQLERR_BADDBMSID |
1 |
unsupported dbmsconid |
SQLERR_DBMSERR |
2 |
dbms error; use SQLOP_GET_ERRMSG for details |
SQLERR_TOOFEW |
3 |
too few parameters |
SQLERR_NOTFOUND |
4 |
image file not found |
SQLERR_NOTINITED |
5 |
library not yet initialized |
SQLERR_ALREADYINITED |
6 |
library already initialized |
SQLERR_TOOMANY |
7 |
exceeded maximum number of connections supported |
SQLERR_NOMEM |
8 |
can't malloc or out of malloc handles |
SQLERR_BADOPCODE |
9 |
no such IMAGE.SBR opcode |
SQLERR_BADHANDLE |
10 |
bad HANDLE passed |
SQLERR_PERR |
11 |
miscellaneous parameter error |
SQLERR_LIBLINK |
12 |
can't dynamically link library |
SQLERR_SYNTAX |
13 |
bad syntax in inparm string |
SQLERR_NORESULT |
14 |
no query results to process |
SQLERR_NOTAVAIL |
15 |
feature not (yet?) available |
SQLERR_BADRESULTS |
16 |
result set info inconsistent or corrupt |
SQLERR_NOCONN |
17 |
no connection has been initialized; see SQLOP_INIT_CONN |
SQLERR_NOSTMT |
18 |
no statement has been allocated |
SQLERR_BADOPTION |
19 |
bad option or flag |
SQLERR_BADRESHDL |
21 |
bad result set handle passed |
SQLERR_BADSTMTHDL |
22 |
bad statement handle passed |
SQLERR_BADSTMTTBL |
23 |
statement table is corrupt |
SQLERR_TOOMANYSTMTS |
24 |
statement table is full |
SQLERR_BADBINDSIZE |
25 |
bad size of variable during binding |
SQLERR_BADBINDSYNTAX |
26 |
bad syntax during binding |
SQLERR_BADBINDTYPE |
27 |
bad variable binding type |
SQLERR_TOOMANYRESHDLS |
28 |
result set table full |
SQLERR_NESTIGNORE |
29 |
nested CLOSE_LIB ignored |
