***:1 - INVALID OPERATION 
  The operation parameter specified in the call is invalid.

***:2 - I/O ERROR 
  An error occurred during a disk read/write.  This status code indicates
  that the file has been damaged and must be recreated, or that the file 
  specified on the open call was not created.  This status code also occurs 
  if the application passed an invalid position block.
  TS - This is a general I/O error and does not necessary mean the file must
  be recreated.

***:3 - FILE NOT OPEN 
  The operation cannot execute because the file is not open.
  A successful Open operation must be performed before Btrieve can process
  any other operations.  This status code also occurs if the application 
  passed an invalid position block.
  TS - Remember to leave a blank space at the end of your Btrieve file spec.  

***:4 - KEY VALUE NOT FOUND 
  The specified key value in the index path was not found.  
  TS - This is a valid error code, and does NOT mean something is wrong.
  This error should be trapped for all GetEqual and other random access 
  read operations.

***:5 - DUPLICATE KEY VALUE 
  A record with a key field containing a duplicate key value cannot be added 
  to an index that does not allow duplicate values. 
  TS - This is a valid error code, and does NOT mean something is wrong.

***:6 - INVALID KEY NUMBER 
  The value stored in the key number parameter is not valid for the file 
  being accessed.  The key number must correspond to one of the keys defined 
  when the file was created or to a suplemental index.

***:7 - DIFFERENT KEY NUMBER 
  The key number parameter changed before a GetNext, GetNextExtended, 
  GetPrevious, GetPreviousExtended, Update, or Delete operation.  
  The operation specified requires the same key number parameter as the 
  previous operation because Btrieve uses positioning information relative 
  to the previous key number.
    If you need to change key numbers between consecutive GetNext, 
  GetNextExtended, GetPrevious, or GetPreviousExtended operations, 
  use a GetPosition operation followed by a GetDirect operation to 
  re-establish position for the new index path.

***:8 - INVALID POSITIONING 
  The current position must be established to update or delete a record.  
  Perform a Get or Step operation to establish the current position.  
  This status code also occurs if the application passed an invalid 
  position block.

***:9 - END OF FILE 
  The operation tried to read past the file boundaries (end-of-file or 
  start-of-file).  When reading a file in ascending order according to an 
  index path, Btrieve returns the last record in that index path.  
  When reading a file in descending order according to an index path, 
  Btrieve returns the first record in the index path.
      The GetExtended or StepExtended operations return this status code if 
  the number of records satisfying the filtering condition is less than the
  number of specified records to be returned and the reject count has not 
  been reached.
  TS - This is a valid error code, and does NOT mean something is wrong.
  This error should be trapped for all GetNext, GetPrevious and other  
  sequential read operations.  This status code is returned AFTER the last 
  (or first in a ReadPrevious) record has been read.  I.e., applications 
  should check for EOF first, and process the record only if not found.  

***:10 - MODIFIABLE KEY VALUE ERROR 
  The operation tried to modify a key field that is defined as nonmodifiable.

***:11 - INVALID FILENAME 
  The filename specified does not conform to filenaming conventions.
  TS - Remember to leave a blank space at the end of your Btrieve file spec.  

***:12 - FILE NOT FOUND 
  The filename specified does not exist.  Check the key buffer parameter to 
  make sure the pathname is terminated with a blank or a binary zero.

***:13 - EXTENDED FILE ERROR 
  Btrieve could not find the extension file for an extended file that the 
  application tried to open.  Extension files must be loaded on the logical 
  disk drive specified when the extension was created.  Both the primary file 
  and its extension file must be online to access an extended file.

***:14 - PRE-IMAGE I/O ERROR 
  The pre-image file could not be created or opened.  There are three 
  possible causes for this error:
  * Btrieve could not create a new pre-image file because your disk is full 
    of the pre-image file is damaged.
  * Btrieve could not open the pre-image file to restore file integrity.  
    If the pre-image file was erased or damaged, Btrieve could not restore
    the files integrity.  In this case, either use the RECOVER command in
    the BUTIL utility to retrieve the damaged file's data records in a
    sequential file or replace the file with its most recent backup.
  * Btrieve could not assign a handle to the pre-image file because Btrieve
    was not started by a user with access rights to the pre-image file.  
  TS - Don't have time to recreate this error, but we've had trouble with
  it in the past using NetWare Btrieve.  I think it's caused by having
  another file in the same directory with the same prefix.  I.e., Btrieve 
  file ACCTING.BTR must NOT have any other file named ACCTING.***.  

***:15 - PRE-IMAGE I/O ERROR 
  An I/O error occured during the pre-imaging function.
  Either the disk is full of the pre-image file is damaged.  
  * If the disk is full, erase any unnecessary files or extend the file to
    gain additional disk space.
  * If the pre-image file is damaged, the integrity of the Btrieve file 
    cannot be ensured.  Either use the RECOVER command in the BUTIL utility 
    to retrieve the damaged file's data records in a sequential file or 
    replace the file with its most recent backup.
    TS - See the description on error 14.

***:16 - EXPANSION ERROR 
  An error occurred while writing the directory structure to disk prior to 
  the creation of the expanded file partition.  Either Btrieve could not 
  close the file or a new page was added to the file and Btrieve could not 
  close and reopen the file to update the directory structure.  
  Check for a disk hardware failure.

***:17 - CLOSE ERROR 
  An error occurred while writing the directory structure to disk prior to 
  closing the file.  Either Btrieve could not close the file or a new page 
  was added to the file and Btrieve could not close and reopen the file to 
  update the directory structure.  Check for a disk hardware failure.  
  This status code may also occur if the application passed an invalid 
  position block.

***:18 - DISK FULL 
  This disk is full, and the file could not be expanded to accommodate the 
  insertion.  Either erase any unnecessary file or extend the file to gain 
  additional disk space.

***:19 - UNRECOVERABLE ERROR 
  An unrecoverable error has occurred.  File integrity cannot be ensured.  
  Either use the RECOVER command in the BUTIL utility to retrieve the damaged 
  file's data records in a sequential file or replace the file with its most 
  recent backup.

***:20 - RECORD MANAGER INACTIVE 
  The operation was not processed because requester or the NetWare Btrieve 
  Record Manager was not loaded.  Load the requester or the Btrieve Record 
  Manager.

***:21 - KEY BUFFER TOO SHORT 
  The key buffer parameter was not long enough to accommodate the key field 
  for the index path requested.  Verify that the length of the key buffer 
  equals the length of the key specified in the key number parameter.  
  This status code can be returned only by certain interfaces.

***:22 - DATA BUFFER LENGTH 
  The data buffer parameter was not long enough to accommodate the length of 
  the data record defined when the file was created.  Verify that the length 
  of the data buffer is at least as long as the file's defined record length.
  * For Get or Step operations, if the data buffer is too short to contain
    the fixed length portion of the record, Btrieve does not return any data
    to the data buffer.  If the record is a variable length record and the 
    data buffer is too short to contain the entire variable length portion 
    of the record, Btrieve returns as much data as it can and a status code 
    22, indicating that it could not return the entire record. 
  * For the Insert operation, Brieve does not insert the record if the data
    buffer is shorter than the fixed length portion of the record.  
  * For the Update operation, if the data buffer is too short to contain the 
    fixed length portion of the record, Btrieve does not update the record.
  * For the Create, Stat, and CreateSupplementalIndex operations, a status
    code 22 indicates that the data buffer is not long enough to contain 
    all the file and key specifications, and the alternate collating 
    sequence definition, if specified.
                                      
***:23 - POSITION BLOCK LENGTH 
  The position block parameter is not 128 bytes long.  This error can only be 
  detected by certain language interfaces.

***:24 - PAGE SIZE ERROR 
  Two possible reasons for this status code:
  * The page size is invalid.  The page size must be a multiple of 512 bytes
    but must be no larger than 4096 bytes.
  * When you set the Btrieve page size configuration, the specified value 
    must be greater than or equal to the page size of the file you plan to 
    create or access.  The value of the configuration option may need to be 
    increased.

***:25 - CREATE I/O ERROR 
  The file specified cannot be created.  Possible causes are a full disk 
  directory or a full disk.  If you are creating a file over an existing 
  file, Btrieve returns this status if the existing file is open or
  flagged transactional.

***:26 - NUMBER OF KEYS 
  The number of keys specified for the page size is invalid.  For standard 
  Btrieve files with a page size of 512 bytes, the number of key segments 
  must be between 1 and 8.  For larger page sizes, the number of key segments 
  must be between 1 and 24.  You must define at least one key without the 
  null attribute.

***:27 - INVALID KEY POSITION 
  The key field position exceeds the defined record length for the file.  
  Either the key position is greater than the record length or the key 
  position plus the key length exceeds the record length.  For key-only 
  files, the key must begin in the first byte of the record (position 1).

***:28 - INVALID RECORD LENGTH 
  The record length is invalid.  The record length specified (plus overhead 
  for duplicates) must be less than or equal to the page size minus 6, 
  or greater than or equal to 4 bytes.

***:29 - INVALID KEY LENGTH 
  The key length is invalid.  The key length specified must be greater than 0 
  and cannot exceed 255.  The length of a binary key must be even.  Btrieve 
  requires that each key page in the file must be large enough to hold at 
  least eight keys.  If the page size is too small to accommodate eight 
  occurrances of the specified key length (plus overhead), either increase 
  the file's page size or decrease the key length.

***:30 - NOT A BTRIEVE FILE 
  The file specified is not a valid Btrieve file.  Either the file was not 
  created by Btrieve or it was created by an earlier version of Btrieve.  
  Another possibility is that the first page of the File Control Record 
  is damaged.

***:31 - FILE ALREADY EXTENDED 
  The file specified has already been extended.  A file can be extended 
  only once.

***:32 - EXTEND I/O ERROR 
  The file cannot be extended.  Possible causes are that the directory or 
  the disk is full.

***:34 - INVALID EXTENSION NAME 
  The filename specified for the extended partition is invalid.

***:35 - DIRECTORY ERROR 
  An error occurred while changing to the directory that contains the 
  Btrieve file.  Either the drive specified in the GetDirectory operation 
  does not exist or the pathname specified in a SetDirectory operation was 
  invalid.
     
***:36 - TRANSACTION ERROR 
  A BeginTransaction cannot be performed because no transactions were 
  specified when NetWare Btrieve was configured.

***:37 - TRANSACTION IS ACTIVE 
  A BeginTransaction was issued while another transaction was active at that 
  station.  Transactions cannot be nested.
 
***:38 - TRANSACTION CONTROL FILE I/O ERROR 
  An error occurred when Btrieve tried to write to the transaction control 
  file.  Possible causes are that the disk is full, the disk is 
  write-protected, or the transaction control file (which was created 
  when Netware Btrieve was loaded) is deleted.

***:39 - END/ABORT TRANSACTION ERROR 
  An End or AbortTransaction operation was issued without a corresponding 
  BeginTransaction operation.

***:40 - TRANSACTION MAX FILES 
  The application tried to update more than the maximum number of files 
  allows within a transaction.  The maximum number of different files that 
  may be updated during a logical transaction is set when NetWare Btrieve 
  is configured.

***:41 - OPERATION NOT ALLOWED 
  The application tried to perform an operation that is not allowed at this 
  time.  Some operations are not allowed under certain operating conditions.  
  For example, Btrieve returns this status code if you attempt to perform a 
  Step, Update, or Delete operation on a key-only file, or a Get on a 
  data-only file.
    Also certain operations are prohibited during transactions because they 
  have too great an effect on the pre-image file, or on Btrieve performance.
  These operations include Close, Set, ClearOwner, Extend, CreateSupplemen-
  talIndex, or DropSupplementalIndex.

***:42 - INCOMPLETE ACCELERATED ACCESS 
  The application tried to open a file that was previously accessed in an 
  accelerated mode, and was never successfully closed.  The file's integrity 
  cannot be ensured.  Either use the RECOVER command in the BUTIL utility to 
  build a new file or restore the file using the latest backup.

***:43 - INVALID RECORD ADDRESS 
  The record address specified for a GetDirect operation is invalid.  
  The address is outside of the file's boundaries; it is not a record 
  boundary within a data page or on a data page.  The 4-byte address you 
  specify for a GetDirect operation should be one that was obtained by a 
  GetPosition operation.

***:44 - NULL KEY PATH 
  The application tried to use the GetDirect operation to establish an index 
  path for a key whose value is null in the corresponding record.  
  Btrieve cannot establish positioning based on a null key value.

***:45 - INCONSISTENT KEY FLAGS 
  The key flags specification on a Create operation is inconsistent.  
  If a key has multiple segments, the duplicate, modifiable, and null 
  attributes should be the same for each segment in the key.

***:46 - ACCESS TO FILE DENIED 
  The application opened a file in the read-only mode, and tried to perform 
  an Update, Delete, or Insert on that file.  Another possible cause is that 
  the owner name required for updates was not specified correctly when you 
  opened the file.

***:47 - MAXIMUM OPEN FILES 
  The number of files open in accelerated mode exceeds the number of buffers 
  available in Btrieve's cache.  When a file in opened in accelerated mode, 
  Btrieve reserves one of its cache buffers for the file.  Btrieve always 
  reserves five empty buffers for index manipulation.  Reconfigure Btrieve 
  with a smaller page size to allocate more buffers.

***:48 - INVALID ALTERNATE SEQUENCE DEFINITION 
  The first byte of an alternate collating sequence definition 
  (the identification byte) did not contain the hexadecimal value AC.

***:49 - KEY TYPE ERROR 
  The application tried to create a file or a supplemental index with an 
  invalid extended key type or tried to assign an alternate collating 
  sequence to a binary key or key segment.  You can assign an alternate 
  collating sequence to string, lstring, or zstring key types only.  
  This status code is also returned if you define a supplemental index 
  requiring an alternate collating sequence, and no alternate collating 
  sequence definition exists either in the file or in the key definition 
  passed in the data buffer.

***:50 - OWNER ALREADY SET 
  The application tried to perform a SetOwner operation on a file that 
  already has an owner.  Use the ClearOwner operation to remove the 
  previous owner before specifying a new one.
                                                 
***:51 - INVALID OWNER 
  There are two possible causes for this status code:
  * If the Btrieve application received this status code after a SetOwner
    operation, the owner names specified in the key buffer and data buffer
    did not match.
  * If the Btrieve application received this status code after an Open
    operation, the file you tried to open has an owner name assigned to it.
    Your application must specify the correct owner name in the data buffer.
  
***:52 - ERROR WRITING CACHE 
  When trying to make a cache buffer available, Btrieve tried to write data 
  to logical disk drive from a file that was previously open in accelerated 
  mode.  An I/O error occured during a write.

***:53 - INVALID INTERFACE 
  An application tried to access a file containing variable length records 
  with a language interface from Btrieve 3.15 or earlier.  To access files 
  with variable length records, you must use a Btrieve v4.xx or later 
  interface.

***:54 - VARIABLE PAGE ERROR 
  During a StepDirect operation, Btrieve could not read all or part of the 
  variable length portion of a record.  In this case, Btrieve returns as 
  much data as possible to your application.  This error usually indicates 
  file damage to one or more pages in a file.

***:55 - AUTOINCREMENT ERROR 
  The application tried to specify either the segmented or variable 
  attribute for an autoincrement key type.  An autoincrement key 
  cannot be part of another key and cannot allow duplicates.

***:56 - INCOMPLETE INDEX 
  A supplemental index is damaged.  This can occur if a 
  CreateSupplementalIndex operation or DropSupplementalIndex operation is
  interrupted and does not run to completion.  Perform a DropSupplemental-
  Index operation to completely remove the index from the file.

***:58 - COMPRESSION BUFFER TOO SHORT 
  The application tried to read or write a record that is longer than the 
  value specified for the size of the compression buffer.  Reconfigure 
  NetWare Btrieve, specifying a higher value for the Maximum Compressed 
  Record Size configuration option.  

***:59 - FILE ALREADY EXISTS 
  This status code is return for the Create operation if you specified -1 in 
  the key number parameter and the name of an existing file in the buffer 
  parameter.

***:60 - REJECT COUNT REACHED 
  Btrieve rejects the number of records specified by the reject count before 
  an Extended Get/Step operation can find the requested number of records 
  that satisfied the filter condition.  Check the first two bytes of the data 
  buffer returned for the number of records that were retrieved.  
  TS - This is a valid error code, and does NOT mean something is wrong.

***:61 - WORK SPACE TOO SMALL 
  The Extended Get/Step operations use the pre-image buffer as work space.  
  The work space buffer is not large enough to hold the filtering data buffer 
  structure and the largest record to be received.  The size of the work 
  space is specified by the Pre-image Buffer Size configuration option.  
  Check the first two bytes of the data buffer returned for the number of 
  records that were retrieved.

***:62 - INCORRECT DESCRIPTOR 
  The descriptor (that is, the data buffer structure), which is passed for 
  an Extended Get/Stop operation, is incorrect.  The descriptor is the data 
  buffer structure that is passed for a Get/Step Next/Previous operation.  

***:63 - INVALID EXTENDED INSERT BUFFER 
  An ExtendedInsert provides an invalid buffer.  Either the buffer length is 
  less than 5 bytes or the number of records specified is zero.

***:64 - FILTER LIMIT REACHED 
  During an ExtendedGet Next/Previous operation, a rejected record was 
  reached.  Furthermore, this rejected record is such that no other record 
  can satify the filtering condition, going in the direction specified by the 
  operation.  This is applicable only if the key specified by the key number 
  is also used as the filtering condition.  
  TS - This is a valid error code, and does NOT mean something is wrong.

***:65 - INCORRECT FIELD OFFSET 
  The field offset in the extractor of an Extended Get/Step operation is 
  invalid based on the length of the retrieved record.

***:74 - AUTOMATIC TRANSACTION ABORT 
  This is an informative status code and is applicable only in the 
  server-based environment.  Btrieve replaced an EndTransaction operation 
  with an AbortTransaction because an error had been detected for a TTS file 
  inside a transaction.  In addition, Btrieve executed the Abort Transaction 
  operation.

***:78 - DEADLOCK DETECTED 
  Btrieve detected a deadlock condition.  The application should clear all 
  resources (such as aborting or ending the transaction or releasing all 
  record locks) before proceeding.  This allows the other applications 
  to access the resources for which they are waiting.

***:79 - PROGRAMMING ERROR 
  This is an internal programming error.  Contact the Novell Development 
  Products Division.  
  TS - As of Spring '94, Novell's Btrieve and NetWare SQL products have been 
  bought out by Btrieve Technologies Inc.  

***:80 - CONFLICT 
  The Update or Delete operation was not performed.  When using Btrieve with 
  DOS, Windows, or OS/2, this status code is returned when another 
  application changes the record on the data page from which you originally 
  read the record that you wanted to update or delete.  In NetWare Btrieve, 
  this status code is returned when the record that you originally read has 
  been changed by another application since you read it.  Your application 
  should reread the record prior to resending an Update or Delete operation.

***:81 - LOCK ERROR 
  This can result from any one of two conditions:
  * The Btrieve lock table is full.  Decrease the number of locks that your
    application uses or reconfigure NetWare Btrieve and specify a higher
    value for the Maximum Number of Record Locks configuration option.
  * The application tried to unlock one record that was locked with a 
    multiple record lock, and the record position stored in the data buffer
    did not correspond to any record that was locked in that file.

***:82 - LOST POSITION 
  When performing a GetNext or GetPrevious on a key with duplicates, the 
  application tried to retrieve a record that was deleted or whose key value 
  was modified by another application.  Restablish position using a GetEqual 
  or a GetDirect operation.

***:83 - READ OUSTIDE TRANSACTION 
  The application tried to update or delete a record within a transaction, 
  but the record was not read within the transaction.  If you are going to 
  update or delete a record within a transaction, you must first read the 
  record within the transaction to ensure you have obtained exclusive 
  access to the data.

***:84 - RECORD LOCKED 
  The application tried to apply a no-wait lock on a record that was 
  currently locked by another application, or to apply a no-wait lock on a 
  file while another application held active record lock(s) in that file.
    If this status code is returned, your application can use either of the
  following two methods:
  * Retry the operation until it is successful.  Under light to moderate  
    network use, this may be the simplest and quickest solution.
  * Use the wait option (+100/+300) instead of the no-wait option.
  TS - This is a valid error code, and does NOT mean something is wrong.

***:85 - FILE LOCKED 
  The application tried to apply a no-wait record or file lock while another 
  application held the file locked.  This status code is also returned when 
  the application tried to open a file outside of a transaction and the file 
  is locked by another application.
    If this status code is returned, your application can use either of the
  following two methods:
  * Retry the operation until it is successful.  Under light to moderate  
    network use, this may be the simplest and quickest solution.
  * Use the wait option (+100/+300) instead of the no-wait option.
  TS - This is a valid error code, and does NOT mean something is wrong.

***:86 - FILE TABLE FULL 
  Btrieve's file table is full.  Reconfigure Btrieve and specify a higher 
  value for the Maximum Number of Open Files configuration option.

***:87 - HANDLE TABLE FULL 
  Btrieve's handle table is full.  Reconfigure Btrieve and specify a higher 
  value for the Maximum Number of File Handles configuration option.


***:88 - INCOMPATIBLE MODE ERROR 
  The application tried to open a file in an incompatible mode.  If the first 
  application to access the file opens it in accelerated mode, all other 
  applications must open it in accelerated mode.  If the first application 
  opens it in non-accelerated mode, other applications cannot open the file 
  in accelerated mode.

***:90 - DIRECTED DEVICE TABLE FULL 
  The Btrieve requester's redirection table or server routing table is full.  
  This occurs if you attach to additional servers or map to additional drives 
  after you've loaded BREQUEST.  Reload BREQUEST specifying a larger number 
  for the Number or File Servers, or the Number of Mapped Drives 
  configuration options (/S and /R, respectively).  This error also occurs 
  if you detach from a particular server and attach to a different server.  
  Once a workstation has attached to a server, BREQUEST will not remove 
  its name from the server routing table.

***:91 - SERVER ERROR 
  BREQUEST could not establish a session with the server.  Either the NetWare 
  Btrieve Record Manager has not been started or the server was not active.  
  Verify that NetWare Btrieve is active on the server.

***:92 - TRANSACTION TABLE FULL 
  The maximum number of transaction was exceeded.  Reconfigure NetWare 
  Btrieve and specify a higher value for the Number of Concurrent 
  Transactions configuration option.

***:93 - INCOMPATIBLE LOCK TYPE 
  Your application tried to mix single record locks (+100/+200) and multiple 
  record locks (+300/+400) in the same file at the same time.  All locks of 
  one type must be released before a lock of the other type can be executed.

***:94 - PERMISSION ERROR 
  Your application tried to open or create a file in a directory without 
  the proper privileges.  Btrieve does not override the network privileges 
  assign to users.

***:95 - SESSION NO LONGER VALID 
  The previously established session was no longer active due to an error at 
  the workstation, the file server, or on the network.  Verify that your 
  workstation is still attached to the file server and then reload the 
  Btrieve requester.  This status code is also returned if the maximum number 
  of sessions for NetWare Btrieve has been reached.  When using NetWare 
  Btrieve in the 286 environment, use the console command BSTATUS to check 
  whether the maximum number of sessions has been reached.  When using 
  NetWare Btrieve in the 386+ environment, use the Status option of the 
  Available Options menu of the BCONSOLE utility to check whether the 
  maximum number of sessions has been reached.  If so, reconfigure NetWare 
  Btrieve to increase the number of available sessions.

***:96 - COMMUNICATIONS ENVIRONMENT ERROR 
  This status code occurs when loading NetWare Btrieve on a NetWare server.  
  The SPX connection table is full.  Reload SPX, specifying a higher value 
  for the connection table.  Refer to the NetWare system documentation for 
  more information.

***:97 - DATA MESSAGE TOO SMALL 
  Your application tried to read or write a record that was longer than 
  NetWare Btrieve or the Btrieve requester could handle.  Reconfigure the 
  Btrieve Record Manager and specify a higher value for the Record Length 
  configuration option.  Reload the requester and specify a higher value for 
  the /D option.  
  * For an Update, Insert, or Create operation, the 
    application receives this error if the data buffer length it specifies for 
    the record exceeds the length specified for the Btrieve Record Manager or 
    BSERVER.
  * For a Get, Step, or Stop operation, the application receives this error 
    if the value specified for the data buffer length is shorter than the  
    length of the data Btrieve would return. , regardless of the data buffer
    length specified in the program.

***:98 - INTERNAL TRANSACTION ERROR 
  An error has been detected while executing a previous operation on a 
  NetWare TTS file.  Therefore, no operation other than 
  AbortTransaction (21) is allowed at this point.

