Cdigo de Errores y Mensajes The following is a table of the error messages generated by the DBISAM database engine, their

corresponding error codes and constants used by DBISAM to represent them, and additional information about the error. Please keep in mind that this list only covers the errors issued by the DBISAM database engine itself and does not cover general database errors issued by the interface units. If you wish to use the error constants defined by DBISAM in your applications for error trapping you need to make sure: For Delphi applications, that the DBISAMCN.DCU file is included in your USES clause for the source unit in question For C++Builder applications, that the DBISAMCN.HPP file is included in your .h header file for the source file in question An important thing to note is that DBISAM uses it's own exception class called EDBISAMEngineError, not the BDEspecific EDBEngineError exception class. The behavior between the the two exception classes is similar except for the fact that the EDBISAMEngineError exception class only contains an ErrorCode property (and some additional context information) whereas the EDBEngineError exception class contains an array of error classes, each with it's own error code. The reason for this is that the BDE can raise multiple error codes in one exception, whereas DBISAM only raises one error per exception. Error ID and Code DBISAM_BLOBLIMIT (9498) Message and Further Details Too many blob fields or invalid blob block size specified for the table '' This error occurs when DBISAM internally attempts to open more blobs than allowed. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. Beginning of table '' unexpectedly encountered This error should not normally occur since encountering the beginning of file in a table is a normal occurrence. The only time this error is triggered is when the beginning of file is encountered unexpectedly. The language driver for the table '' is not available or installed This error occurs when an attempt is made to open or create a table with a language ID that is not available or installed on the current machine's operating system. Certain languages are only available on certain language-specific versions of the Windows 95/98/ME or Windows NT/2000 operating systems. Error compressing data This error occurs when the database engine attempts to compress a data buffer and the compression fails. This error should never occur, so if you receive this error you should immediately contact Elevate Software for more information on how to resolve this issue. End of blob data in the table '' reached prematurely This error occurs when the DBISAM database engine expects blob data to be x number of bytes in length but encounters the end of the data before reaching the desired number of bytes. The most likely cause of this error is corruption in the table (in which case you should use the Database System Utility to repair the table). End of table '' unexpectedly encountered This error should not normally occur since encountering the end of file in a table is a normal occurrence. The only time this error is triggered is when the end of file is encountered unexpectedly. An error occurred during the export from the table '' This error occurs when any error occurs during the export of a table to an external text file. The message will give the specific details of the error and why the error occurred. Data record buffers corrupt in the table '' This error occurs when the DBISAM database engine attempts read, write, or manipulate an internal record buffer and cannot do so due to the structure of the data being corrupted. You should use the Database System Utility to repair the table if this error occurs. Cannot delete the table '' This error code is no longer in use. Error accessing header information for the table ''

DBISAM_BOF (8705)

DBISAM_CANNOTLOADLDDRV (15878)

DBISAM_COMPRESS (15001)

DBISAM_ENDOFBLOB (8711)

DBISAM_EOF (8706)

DBISAM_EXPORTERROR (11301)

DBISAM_FILECORRUPT (8962)

DBISAM_FILEDELETEFAIL (9220) DBISAM_FILENOACCESS (9221)

This error occurs when the DBISAM database engine attempts read, write, or manipulate an internal index page buffer and cannot do so due to the structure of the data being corrupted. You should use the Database System Utility to repair the table if this error occurs. DBISAM_INDEXEXISTS (10027) The secondary index '' already exists for the table '' This error occurs when an attempt is made to add a new secondary index and the secondary index name already exists in the table. All secondary indexes require a unique name (case-insensitive) that is used to identify the index. DBISAM_INDEXLIMIT (9487) Maximum or minimum limits on number of indexes or fields in an index exceeded in the table '' This error occurs when an attempt is made to add a new secondary index or create a new table and doing so would exceed the maximum number of indexes or the maximum number of fields per index that can be present in a table. If you receive this error you should consult the System Capacities topic for more information on the limits for indexes. DBISAM_INDEXNAMEREQUIRED (10010) The secondary index name is missing or not specified for the table '' This error occurs when an attempt is made to add a new secondary index and the secondary index name is missing or not specified. All secondary indexes require a unique name (case-insensitive) that is used to identify the index. DBISAM_INTERNALLIMIT (9482) Too many filters defined for the table '' This error occurs when DBISAM internally attempts to define more filters than allowed. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. DBISAM_INVALIDBLOBHANDLE (10030) Invalid blob handle for the table '' specified This error occurs when DBISAM internally attempts to modify an open blob with an invalid handle to the open blob. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. DBISAM_INVALIDBLOBLEN (10029) Invalid blob length in the table '' This error occurs when the DBISAM database engine attempts to access blob data in the table and the length of the blob data it is trying to access is invalid. This error should never occur, however if it does the most likely reason is corruption in the file that has mangled internal pointers so that they point beyond the end of the file or are 0. You should use the Database System Utility to repair the table if this error occurs. DBISAM_INVALIDBLOBOFFSET (9998) Invalid blob offset into the table '' specified This error occurs when the DBISAM database engine attempts to access blob data in a table and the offset at which it is trying to access the data is invalid. This error should never occur, however if it does the most likely reason is corruption in the file that has mangled internal pointers so that they point beyond the end of the file or are 0. You should use the Database System Utility to repair the table if this error occurs. DBISAM_INVALIDFIELDNAME (10038) Invalid or duplicate field name '' specified for the table '' This error occurs when an attempt is made to define the specified field with an invalid or duplicate field name. An example of an invalid field name is a blank field name or a field name that starts with an invalid character such as a digit. DBISAM_INVALIDFILTER (10051) Filter error for the table '' This error occurs when an invalid filter statement is passed to the DBISAM engine. The most common cause of this error is improperly formatted date, time, or number constants or some other type of syntax error. DBISAM_INVALIDFLDTYPE (10000) Invalid field definition specified for the field '' in the table '' This error occurs when an attempt is made to create a new table or restructure and existing table and a field definition is invalid due to a bad field type or a length that exceeds the maximum limits for fields. If you receive this error you should consult the System Capacities topic for more information on the limits for the length of fields.

encryption cannot be blank and must be less than or equal to 15 characters in length. DBISAM_INVALIDVCHKSTRUCT (10006) Invalid default, min or max validity check, or expression specified for the field '' in the table '' This error occurs when a default value, minimum check, or maximum check expression for the indicated field is invalid. You need to verify that the expression provided is appropriate for the data type of the indicated field. If the expression contains constants, you need to verify that the expression is properly formatted, especially with date, time, or number expressions. DBISAM_KEYORRECDELETED (8708) Record has been changed or deleted by another user, session, or table cursor in the table '' This error occurs when the database engine attempts to edit or delete a record and the record has already been changed or deleted by another user since the database engine last cached the record. DBISAM_KEYVIOL (9729) Duplicate key found in the index '' of the table '' This is a non-fatal error that occurs when an attempt is made to add a record to a table and the record would cause a duplicate key to be added for the primary index or for a secondary index that it is defined as being unique. Primary indexes implicitly enforce uniqueness and therefore cannot permit duplicates to be added, while secondary indexes must be explicitly defined as unique. DBISAM_LOCKED (10241) The table '' is already locked by another user This error occurs when an attempt is made to lock a table that is already locked by another application or the same application. This error will also occur if an attempt is made to lock a table and there are individual record(s) locked in the table. DBISAM_LOCKTIMEOUT (10249) General lock failure with the table '' This error occurs when an internal read or write lock on a table fails. This error will occur if a transaction is active on a table for an inordinate amount of time, such as when a transaction is forced to wait for user input. You should always make sure to not have a transaction active during a period of user input in order to avoid this error. DBISAM_MAXVALERR (9731) The value for the field '' in the table '' is above the maximum allowable value This is a non-fatal error that occurs when an attempt is made to add a record to a table and a field in the record would violate a maximum value validity check for that field. Validity checks ensure that data is either present or within an approved range of values for any given field. DBISAM_MEMOCORRUPT (8963) BLOB block buffers corrupt in the table '' This error occurs when the DBISAM database engine attempts read, write, or manipulate an internal BLOB block buffer and cannot do so due to the structure of the data being corrupted. You should use the Database System Utility to repair the table if this error occurs. DBISAM_MINVALERR (9730) The value for the field '' in the table '' is below the minimum allowable value This is a non-fatal error that occurs when an attempt is made to add a record to a table and a field in the record would violate a minimum value validity check for that field. Validity checks ensure that data is either present or within an approved range of values for any given field. DBISAM_NEEDEXCLACCESS (10253) The table '' must be opened exclusively This error occurs when an attempt is made to perform an operation on a table that requires the table to be opened exclusively in order to complete the operation. The operations that require exclusive use of the table are as follows: Creating Emptying Repairing Adding a primary or or a a verifying secondary index a to a table table table table

DBISAM_NOTINITIALIZED (10758)

DBISAM_NOTSUFFTABLERIGHTS (10498)

DBISAM_OLDVERSION (12035)

DBISAM_OPENBLOBLIMIT (9494)

DBISAM_OSEACCES (11013)

DBISAM_OSEBADF (11014)

DBISAM_OSEINVMEM (11017) DBISAM_OSEMFILE (11012)

DBISAM_OSENODEV (11023)

DBISAM_OSENOENT (11010)

DBISAM_OSENOMEM (11016)

DBISAM_OSENOTSAM (11025)

DBISAM_OSUNKNOWN (11047)

perform a blob operation on a field that is not a blob field. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. The database engine is not initialized This error occurs when an attempt is made to use the DBISAM Database System without first intializing the database engine. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. Insufficient rights to the table '', a password is required This error occurs when an attempt is made to perform an operation on an encrypted table and a valid password has not been provided. You can add new passwords for the current session using the OnPassword event or AddPassword method of the TDBISAMSession component. The table '' is not the correct version This error occurs when an attempt is made to open a table that is either the incorrect version for the current DBISAM engine or is not a DBISAM table at all (but may have the same extension of .DAT). Too many blobs opened in the table '' This error occurs when DBISAM internally attempts to open more blobs than allowed. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. Access denied to table '' This error usually occurs when an attempt is made to open up a table that has already been opened up exclusively by another application or the same application. A table can be opened exclusively only once. It can also occur when an attempt is made to open up a table for read/write access that is in a read-only directory or on a read-only drive and not marked as read-only as an attribute. Invalid operating system file handle for the table '' This error occurs when DBISAM internally attempts to perform an operation on a table using an invalid file handle. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. Invalid length for the in-memory table '' This error code is no longer in use. Too many operating system files open while attempting to open the table '' This error occurs when an attempt is made to open up a table and the operating system rejects the open because it has run out of available file handles. If you receive this error you should consult the System Capacities topic for more information on the limits for the number of open tables. Access denied to logical operating system device for the table '' This error occurs when the operating system reports that the logical device for the table is invalid or inaccessible. This problem can occur with removable disks in floppy drives or CD-ROM drives. Table '' does not exist This error occurs when an attempt is made to open up a table that does not exist. There is insufficient operating system memory available for the current operation This error occurs when there is insufficient memory available from the operating system to complete the current operation. If you receive this error you should contact Elevate Software in order to find out how to reduce the amount of memory being consumed and to find alternate solutions to the problem. The table '' has been moved This error occurs when the operating system detects that a file has been moved from one device to another after being opened. This error should essentially never occur. An unknown operating system error occurred with the table '' This error occurs when DBISAM detects an operating system error but cannot identify it. Examples of this may include operating system errors

DBISAM_RECNOTFOUND (8710)

DBISAM_RECTOOBIG (9477)

DBISAM_REMOTEADDRESSBLOCK (11283)

DBISAM_REMOTECALLBACKERR (11285)

DBISAM_REMOTECOMMLOST (11276)

DBISAM_REMOTECONNECT (11280)

DBISAM_REMOTEDUPDB (11295)

DBISAM_REMOTEDUPDBUSER (11298)

DBISAM_REMOTEDUPUSER (11292)

DBISAM_REMOTEINVDB (11293)

DBISAM_REMOTEINVDBUSER (11296)

DBISAM_REMOTEINVLOGIN (11287)

This error occurs when an attempt is made to lock a record in a table that is already locked by another application or the same application. Record not found in the table '' This error occurs when when a call to the GotoCurrent method of the TDBISAMTable components fails to find the corresponding record in the passed destination table. Please see the DBISAM Component Reference help file for more information on the GotoCurrent method and it's restrictions. Maximum record size exceeded in the table '' This error occurs when an attempt is made to create a new table or restructure an existing table and doing so would exceed the maximum allowable record size. If you receive this error you should consult the System Capacities topic for more information on the limits for record sizes. A connection to the database server at '' cannot be established, the client address is blocked This error occurs in the Client/Server version of DBISAM when an application attempts to connect to a remote server via a TDBISAMSession component and the connection fails because the IP address of the machine the application is running on has been blocked by the server administrator. A server callback error occurred for the database server at '' This error occurs in the Client/Server version of DBISAM when an internal callback used by the client and server processes fails for some reason. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. The connection to the database server at '' has been lost This error occurs in the Client/Server version of DBISAM when an application attempts an operation on a remote server and the operation fails. This is most often caused by a physical interruption in the connection between the client and server processes. A connection to the database server at '' cannot be established This error occurs in the Client/Server version of DBISAM when an application attempts to connect to a remote server via a TDBISAMSession component and the connection fails. This is most often caused by the lack of a server process listening on the specified port at the specified IP address. The database '' already exists on the database server at '' This error occurs in the Client/Server version of DBISAM when an attempt is made to add a new logical database to a remote server and the database name (case-insensitive) already exists on that remote server. The database user '' already exists for the database '' on the database server at '' This error occurs in the Client/Server version of DBISAM when an attempt is made to add a new user to a logical database on a remote server and the user name (case-insensitive) already exists for the specified logical database on that remote server. The user '' already exists on the database server at '' This error occurs in the Client/Server version of DBISAM when an attempt is made to add a new user to a remote server and the user name (case-insensitive) already exists on that remote server. The database name is either invalid or blank This error occurs in the Client/Server version of DBISAM when an attempt is made to add a new logical database to a remote server and the database name is either missing or invalid. The database user name is either invalid or blank This error occurs in the Client/Server version of DBISAM when an attempt is made to add a new user to a logical database on a remote server and the user name is either missing or invalid. A connection to the database server at '' cannot be established, the login information provided is invalid This error occurs in the Client/Server version of DBISAM when an

DBISAM_REMOTENODB (11294)

DBISAM_REMOTENODBUSER (11297)

DBISAM_REMOTENOLOGIN (11281)

DBISAM_REMOTENOTADMIN (11289)

DBISAM_REMOTENOTAUTH (11288)

DBISAM_REMOTENOUSER (11291)

DBISAM_REMOTEUNKNOWN (11279)

DBISAM_REMOTEVERSION (11286)

DBISAM_REQDERR (9732)

DBISAM_SEARCHCOLREQD (12292)

DBISAM_SQLPARSE (11949)

DBISAM_TABLEEXISTS (13060)

The database '' does not exist on the database server at '' This error occurs in the Client/Server version of DBISAM when an application attempts to reference a logical database on a remote server that does not exist. The database user '' does not exist for the database '' on the database server at '' This error occurs in the Client/Server version of DBISAM when an application attempts to reference a user defined for a logical database on a remote server that does not exist. A connection to the database server at '' cannot be established, the server is not accepting new logins This error occurs in the Client/Server version of DBISAM when an application attempts to connect to a remote server via a TDBISAMSession component and the connection fails because the server administrator has set the server to refuse any new logins. The user '' is not authorized to perform administration functions on the database server at '' This error occurs in the Client/Server version of DBISAM when an application attempts to perform an administrative function on a remote server via a TDBISAMSession component and it fails because the user is not designated as an administrator for that server. The user '' is not authorized to perform this operation with the database '' on the database server at '' This error occurs in the Client/Server version of DBISAM when an application attempts to perform a function on a remote server and it fails because the user is not designated as having rights to perform such a function on the current logical database. The user '' does not exist on the database server at '' This error occurs in the Client/Server version of DBISAM when an application attempts to reference a user on a remote server that does not exist. An unknown error ('') occurred with the connection to the database server at '', please check the server log This error occurs in the Client/Server version of DBISAM when an unknown error has occurred during operations between the client and server processes. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. A connection to the database server at '' cannot be established, the client engine version does not match the server This error occurs in the Client/Server version of DBISAM when an application attempts to connect to a remote server via a TDBISAMSession component and the connection fails because the database engine version of the client does not match that of the remote server. DBISAM requires that the client and server processes must both be using the same database engine version in order to prevent any inconsistencies or errors that might result from using mismatched engine versions. A value must be provided for the field '' in the table '' This is a non-fatal error that occurs when an attempt is made to add a record to a table and a field in the record would violate a required value validity check for that field. Validity checks ensure that data is either present or within an approved range of values for any given field. Invalid field type specified for the index '' in the table '' This error occurs when an attempt is made to add a secondary index or create a table with a primary index that contains blob fields as one or more of the index fields. Blob fields cannot be directly indexed in DBISAM. SQL error This error occurs when any error occurs during the parsing, preparation, or execution of an SQL statement. The message will give the specific details of the error and why the error occurred. The table '' already exists

Optimizing

table

DBISAM_UNCOMPRESS (15002)

DBISAM_UNLOCKFAILED (10242)

DBISAM_WRITEERR (9218)

Upgrading a table Error uncompressing data This error occurs when the database engine attempts to uncompress a data buffer and the uncompression fails. This error should never occur, so if you receive this error you should immediately contact Elevate Software for more information on how to resolve this issue. Cannot unlock table or record in the table '' This error occurs when DBISAM cannot unlock a record in a table or the entire table itself. This error should never occur so if it does you should contact Elevate Software immediately for a resolution to the problem. Error writing to the table '' This error occurs when the DBISAM database engine attempts to write to the table and cannot write the desired number of bytes. This error should never occur, however if it does the most likely reason is corruption in the file that has mangled internal pointers so that they point beyond the end of the file. You should use the Database System Utility to repair the table if this error occurs.

The data on this web page was last updated on Tuesday, September 11, 2001 at 03:43 PM Questions or comments ? E-mail us at mailto:%20info@mail.elevatesoft.com 2001 Elevate Software All Rights Reserved