[Previous] 

10    Too Many Nested BEGIN SEQUENCE/END Blocks
Too many nested BEGIN SEQUENCE/END blocks have been defined. The maximum is 16. 
Note: The usual reason this occurs is a LOOP statement within a BEGIN SEQUENCE/END structure like the following: 
   DO WHILE <condition>
      <statements>...
      BEGIN SEQUENCE
         <statements>...
         LOOP
      END <statements>...
   ENDDO
 

11    BEGIN SEQUENCE/END Integrity Error
An underflow of BEGIN SEQUENCE stack has occurred. This only happens if there is a pending END without a BEGIN SEQUENCE. 

12    Evaluation stack underflow after BEGIN SEQUENCE/END
Occurs after a BREAK. 

14    SORT Error
The system ran out of memory during a SORT operation while attempting to allocate a database buffer. 

15    SORT Error
Memory corruption has occurred during a SORT operation. 

16    Database Not Open
This occurs at the end of a large block database operation (such as APPEND, JOIN, UPDATE, or TOTAL) and one of the database files used in the operation is no longer open. 
Action: Check user-defined function used within the erroneous statement for any statements that close database files. 

17    NTX File Corrupted
This occurs when an index buffer is found to be corrupted when attempting to update an index page. 

18    NTX File Corrupted
This occurs when an index buffer is found to be corrupted when attempting to update an index page, and the index is UNIQUE. 

19    NTX File Corrupted
This occurs when an index buffer is found to be corrupted when attempting to update an index page, and the index is non-UNIQUE. The index file can be "corrupted" by creating it while the table is opened in shared mode. Indexes should be created with the file opened exclusively. 

20    NDX File Key Type Error
An evaluation of a key in an .NDX file does not result in a character or number. This can only occur if the key is a logical value. 

21    NDX File Key Type Error
A SEEK expression evaluates to a different data type than the index expression. 

22    NTX File Key Type Error
A SEEK expression in an .NTX file evaluates to a logical, or the system runs out of memory when evaluating the key expression. 

24    Write Error
This error occurs when a CA-Clipper application is unable to write to a database file or to an index file. 
Action: Check that sufficient disk space and directory entries are available. Make sure that the file is not marked read-only. In a network environment, make sure the application has the necessary rights to write to the file and all network connections are correct. 
See Also: "Network Programming" chapter in the Programming and Utilities Guide.
[Next]

Home Web Design Programming Fairlight CMI Soap Box Downloads Links Biography About... Site Map

Site Map Send comments about this site to Greg at gregh@ghservices.com
All pages copyright © 1996-1999 GH Services™   Created 1997/09/28   Last updated 1999/09/30
All trademarks contained herein are the property of their respective owners