SQL Access Manager result codes and messages
- Last UpdatedJun 17, 2024
- 3 minute read
The following table lists some common SQL Access result codes, their corresponding error messages, and descriptions:
|
Result Code |
Error Message |
Description |
|---|---|---|
|
0 |
No errors occurred |
The SQL function ran successfully without errors. |
|
-1 |
<Message from the database provider> |
A specific error message from the vendor database. |
|
-2 |
An empty statement cannot be executed |
A SQLExecute(ConnectionId, BindList, 0) |
|
-4 |
Value returned was Null |
An integer or real value read from the database is null. This is only a warning message sent to the Log Viewer. |
|
-5 |
No more rows to fetch |
The last record in the table has been reached. |
|
-7 |
Invalid parameter ID |
The SQLSetParamChar(), SQLSetParamDate(), SQLSetParamDateTime(), SQLSetParamDecimal(),
SQLSetParamFloat(), SQLSetParamInt(), SQLSetParamLong(), SQLSetParamNull(), |
|
-8 |
Invalid parameter list |
Example of an invalid parameter list: 1, 2, 3, 5 (Missing 4). |
|
-9 |
Invalid type for NULL parameter |
The SQLSetParamNull function is called with an invalid Type argument value. |
|
-10 |
Changing data type of parameter is not allowed |
The SQLSetParamChar(), SQLSetParamDate(), SQLSetParamDateTime(), SQLSetParamDecimal(),
SQLSetParamFloat(), SQLSetParamInt(), SQLSetParamLong(), SQLSetParamNull(), |
|
-11 |
Adding parameter after the statement has been executed successfully is not allowed. |
The SQLSetParamChar(), SQLSetParamDate(), SQLSetParamDateTime(), SQLSetParamDecimal(),
SQLSetParamFloat(), SQLSetParamInt(), SQLSetParamLong(), SQLSetParamNull(), |
|
-12 |
Invalid date time format |
An invalid date time format is encountered, for example, when executing SQLSetParamTime(),
SQLInsertExecute(), |
|
-13 |
Invalid decimal format |
An invalid decimal format is encountered, |
|
-14 |
Invalid currency format |
An invalid currency format is encountered, for example, when executing SQLInsertExecute() or SQLUpdateCurrent(). |
|
-15 |
Invalid statement type for this operation |
SQLInsertEnd is called for a statement ID created by SQLPrepareStatement() |
|
-1001 |
Out of memory |
There is insufficient memory to run this function. |
|
-1002 |
Invalid connection |
The value passed to the ConnectionId argument is not valid. |
|
-1003 |
No Bind List found |
The specified Bind List name does not exist. |
|
-1004 |
No template found |
The specified Table Template name does not exist. |
|
-1005 |
Internal Error |
An internal error occurred. Call Technical Support. |
|
-1006 |
String is null |
Warning - the string read from the database is null. This is only a warning message sent to the Log Viewer. |
|
-1007 |
String is truncated |
Warning - the string read from the database is longer than 131 characters and is truncated when selected. The warning is sent to the Log Viewer. |
|
-1008 |
No Where clause |
There is no Where clause on Delete. |
|
-1009 |
Connection failed |
Check the Log Viewer for more information about the failed connection to the database. |
|
-1010 |
The database specified on the DB= portion of the connect string does not exist |
The specified database does not exist. |
|
-1011 |
No rows were selected |
A SQLNumRows(), SQLFirst(), SQLNext(), SQLLast(), or SQLPrev() function is called
without running a SQLSelect() |
|
-1013 |
Unable to find file to load |
The SQLLoadStatement() function is called with a file name that cannot be found. |
Error messages from a vendor database return a ResultCode of -1. The SQL Access function ResultCode is always -1, but the message is copied exactly from the database provider.
For error messages that occur when using an Oracle database, refer to Oracle Server documentation for specific error messages and solutions.
The following table lists common error messages that can occur when using a Microsoft SQL Server or Access database.
|
Error Message |
Solution |
|---|---|
|
You cannot have more than one statement active at a time |
You are trying to run a SQL command after calling the SQLSelect() function. Run SQLEnd() to free system resources from the SQLSelect() or use a separate ConnectionId for the second statement. |
|
There is not enough memory available to process the command |
Try rebooting the client workstation. |
|
Invalid object name table name |
The table name does not exist in the database you are using. Try DB=database name. |
Check your Microsoft SQL Server documentation for specific error messages and solutions.