Error codes
- Last UpdatedJul 22, 2024
- 3 minute read
Various API scripting methods return an error code as a numeric value.
Methods with syntax descriptions that begin with "result" return these numeric values.
This table shows the numeric value, its corresponding error, and meaning of each error code.
|
Numeric |
Error text and description |
|---|---|
|
-1 |
Unknown Failure This value indicates an exception whose reason could not be determined at run time. |
|
0 |
Success This value indicates a good result; no error occurred. |
|
100 |
SoftwareError This indicates that the internal code returned an unexpected result, but the case was handled. |
|
1000 |
StatementNotReady This error is returned when an aaDBCommand object is run, but it is not properly prepared for processing. |
|
1001 |
StatementFailed This error is returned when an aaDBCommand object runs and fails to complete properly. This result occurs when the SQL query is malformed. |
|
1002 |
DatasetIsNull This error is returned when the results of an aaDBCommand object are being examined or manipulated, but no dataset is associated with the object. This message can mean that the command has not yet run, the SQL query was malformed, or the object was not of a type to return data. |
|
1003 |
DatasetIsEmpty This error occurs when the currently selected row or table number is beyond the end of the data in the dataset that is associated with the aaDBCommand object. |
|
1004 |
InvalidConnection This error is returned when an aaDBCommand attempts to run and the connection object it is attached to has not established a good connection to the database. |
|
1005 |
InvalidRowNum This error is returned by aaDBCommand.SelectRow() when the row number specified is negative or larger than the number of rows in the dataset that is associated with the aaDBCommand object. |
|
1006 |
InvalidColValue This error is returned when a column is examined or manipulated by the index and the index does not represent a valid column number. |
|
1007 |
InvalidTableNum This error is returned by aaDBCommandSelectTable() when the table number does not represent a table that is currently stored in the dataset that is associated with the aaDBCommand object. |
|
1008 |
MissingParameter This error is returned when an OLEDB style aaDBCommand object is run and not all parameter indexes were supplied. |
|
1009 |
NamedParametersNotSupported This error is returned when an attempt is made to call SetXXXParameterByName() for a non-OLEBB style aaDBCommand object. |
|
1010 |
ParameterNameIsRequired This error is returned when an attempt is made to call SetXXXParameterByIndex() for a non-OLEBB style aaDBCommand object. |
|
1011 |
InvalidRequestOperationInProgress This error is returned when an attempt is made to run an aaDBCommand object that is currently processing. If a command or transaction is currently in progress through ExecuteAsync(), that same object cannot be executed again with ExecuteAsync() or ExecuteSync() until the previous process is complete. Only a single object can be in the processing queue at any time. |
|
1012 |
SaveChangesNotSupportedForStoredProcedure This error is returned when either SaveChangesSync() or SaveChangesAsync() is called after manipulating the dataset associated with an aaDBCommand object whose query was originally against a stored procedure. |
|
1013 |
InvalidRequestNotSupportedInCurrentState This error is returned when the aaDBCommand object is not in a state where the requested run or cancel can be honored. |
|
1014 |
InvalidRequestPartOfTransaction This error indicates that you attempted to run or save changes to an aaDBCommand object that was created to be part of an aaDBTransaction. This activity is not permitted. |
|
1015 |
DCMObjectInvalid This error indicates that the DCM cannot provide an object to support aaDBConnection, aaDBCommand, aaDBTransaction. |
|
1016 |
ObjectIsDisposed The script attempted to use an object after calling Dispose(). |