[Previous]

1010     Read/write in index page failed
Action: Check for memory conflicts that could cause a corruption of the index buffer. Try disabling the EMS with the //E:0 in SET CLIPPER. If using third-party RDDs, try increasing the stack space. If using structural indexes (.CDX, .MDX), delete the index file and recreate.


1011     Read/write access in index page failed
CA-Clipper has attempted to read or write to an index page. This error can occur if a the stack has become corrupted or there is insufficient stack space. This may be due to a corrupted or invalid .EXE. 
Action: Try increasing the STACK or PROCEDURE DEPTH. Check for memory conflicts that could cause a corruption of the index buffer. Try disabling the EMS with the //E:0 in SET CLIPPER. If using third-party RDDs, try increasing the stack space. If using structural indexes (.CDX, .MDX), delete the index file and recreate. Resolve all linker warnings and errors. Recompile all .OBJs and relink. Check all third party RDD version compatibility.


1020     Record not found
This error indicates one of the following conditions: 
1) Invalid record number data type specified in DBGOTO(); 
2) Invalid field data type encountered when loading a field from disk to memory; or 
3) Invalid field data type encountered when storing a field from memory to disk. 
Action: Delete indices and recreate. Check for memory conflicts that could cause a corruption of the index buffer. Try disabling the EMS with the //E:0 in SET CLIPPER. If using third-party RDDs, try increasing the stack space. If using structural indexes (.CDX, .MDX), delete the index file and recreate. 
Note: This error is applicable to the DBFNTX replaceable database driver (RDD), and may not be applicable to other RDDs.


1101     Maximum workareas exceeded
CA-Clipper supports 250 work areas. This error can be produced if this limit is exceeded. This usually indicates that an internal process tried to access a field which does not exist, or that an internal field structure is not valid for the work area. This means the runtime system is out of work areas for work area index strings. 
Action: A good place to start looking is in the third-party RDD or any "in house" C/ASM code. Make sure the database driver was REQUESTed and linked. Check the .LIBrary link order.


1102     Requested RDD not linked
A database driver was specified, but that driver is not linked into the application.


1112    Read value larger than 64kb
A read of a variable with length larger than 64kb was attempted. The limit for character variables and memo fields is 64kb. 
Action: This read error could indicate an index access failure indicating a bad FIELD type, i.e., INDEXing on a MEMO or large character field. Look into third-party RDD or any "in house" C/ASM code. Make sure the REQUESTed database driver was linked and check the .LIBrary link order.


1201    No master index in use
An operation, such as a SEEK, was performed in the work area but there was no master or controlling index order. 
Action: Make sure that the index ORDER is not ZERO, or nullified, or that the current TAG (set with SET ORDER TO) was not deleted within a multi-tag index.


1202    Fatal runtime error
This error has occurred in a CA-Clipper 5.2e application linked with Blinker 3.30, CA-Tools, and SuperClass. It appeared suddenly, probably due to a configuration change. Its numbering in the 1200 series indicates that it is index related. Index corruption may have occurred. 
Investigations are ongoing. 
Action: Delete the index file(s) and re-create. Examine memory configuration for anomalies.


1210    Data and Index files out of sync
Database (DBF) files and index (NTX) files are out of sync. This usually happens when the database is updated without the index being open. 
There have been reports of this error being caused by opening multiple index (*.ntx and *.ndx) files in varying order. It is a good idea to open all index files in the same order every time the database is opened. 
Or there is a stack corruption or access problem related to the RDD loaded. 
The error may occur after a record is updated and it is being unlocked. 
Action: Some suggestions to resolve the problem are: 
1) If the cause of this problem is that the database is being updated through a utility external to the application, simply recreate the index file and restart the application. 
2) If the database was not updated outside of the application, check the code for the application to ensure that all indexes are open when updates are being done. Correct the code, recreate the index files, and restart the application. 
3) Check that ALL index key expressions are a constant length. Usage of LTRIM(), RTRIM(), TRIM(), ALLTRIM(), STR(), and DTOC() can all produce expressions that are not a constant length. The TRIM() functions should all be padded out to a constant width using PADR(). 
4) Use all three arguments to STR(). 
5) Use DTOS() instead of DTOC() in index key expressions. DTOC() is dependent upon the SET DATE FORMAT. 
Note: This error is applicable to the third party replaceable database drivers (RDDs), and may not be applicable to CA-Clipper RDDs. This may mean the stack was corrupted, preventing the application from accessing the RDD's index expression. Increase the STACK or PROCEDURE DEPTH. Look for missing or incorrectly ordered .LIBraries, or loading a mismatched RDD. 
If using the DBFCDX driver that came with Clipper before 5.3 (i.e., the Successware/Luxent driver), get the latest version. The Successware driver requires a higher stack size. The official recommendation is 80, but a setting over 110 may eliminate the errors. Put BLINKER PROCEDURE DEPTH 110 in your link script if using Blinker.


1240    Index key evaluation error
An error occurred during index key calculation. This can also be caused by a corrupted header in the .DBF file can cause this. INDEX ON with an EVAL clause not returning a logical true (.T.) will also cause this error. 
Action: Check the index key to ensure it is not on a logical field. Rebuild the .DBF file in the DBU utility, or with DBCREATE(), not COPY STRUCTURE, then append records.


1242    Data type mismatch on key replacement
An attempt was made to replace a key field in the database with an invalid data type. Indexing on a logical field may also cause this error. 
Action: Test the index keys and the replacement values in the debugger.


1255    Damaged index header
This is caused by an index key expression greater than 255 characters. 
Action: Recreate the index file, not exceeding the key expression limit. 
See Also: "CA-Clipper Technical Specifications" appendix, check third party documentation.


2155     Read error on index heading page
A read error occurred when reading the heading page of the index file, or the header did not contain the .NTX signature, or the macro compiler returned a syntax error when attempting to compile the key expression. 
Also, the file may be open in another area. If one work area creates an index, then another work area tries to open that newly created index, you can get this error. 
Action: Recreate the index file and check the key expression. Make sure the database header is updated before index recreation.


4001    Number of METHODs exceeded
An error occurred when accessing more than 32 methods for an instantiation of a class object at runtime. 
Action: CA-Clipper allows no more than 32 methods for any class object at runtime. Check for third party Class .LIBraries and creation of new methods for additional classes. A typographical error or using the SEND operator may mistakenly cause identification of an erroneous method.


4406     Temp file read error
An error occurred when reading from a temporary file. This error is most likely to occur when the disk where the temporary files are written is full. 
Action: Free up the necessary space on the drive for the temporary file, or redirect the temporary file to a different drive via the TEMPPATH option of the CLIPPER environment variable. Check file ownership and rights if on a network.


4412     Indexing miscalculation
This error occurs during indexing if there has been a miscalculation of how indexing should occur. 
Action: Some suggestions to resolve the problem are: 
1) Try increasing available conventional memory for indexing operation. 
2) Try indexing using a small test program. 
3) Test recreating the index with one more or one less database record. 
4) Test recreating the index with one more or one less byte in the key expression. 
5) Test adding CHR(0) to the key. 
6) Test with the E:0 parameter in the SET CLIPPER environment variable. 
This error may be a "magic number" type of error. It's possible that this error will disappear if more or less records are present in the database. Thus, suggestions 3, 4, and 5 attempt to alter the length of the file. 
Note: LEN(CHR(0)) is one byte, LEN("") is 0 bytes. Test with combinations of the above suggestions. 
See Also: "The Runtime Environment" chapter of the Programming and Utilities Guide.


4414     Indexing miscalculation
This error occurs during indexing or sorting if there has been a miscalculation of how indexing should occur. It will occur if the free conventional memory is insufficient to contain the .DBF record information. It usually occurs when indexing or sorting long field length .DBF files because there is not enough memory to contain the information for the record. 
Action: Some suggestions to resolve the problem are: 
1) Increase available conventional memory for indexing or sorting operation. 
2) Try a protected mode version of application. 
This error may be a "magic number" type of error. It's possible that this error will disappear if more or less records are present in the database. 
See Also: Error 4412.


4424     Temp file creation error
An error occurred when creating temporary file for indexing or sorting. This error can occur for several reasons: insufficient file handles, an invalid TEMPPATH or insufficient network rights for the directory where temporary files are created. Note that temporary files are created in the current directory if no TEMPPATH is specified. 
Action: Correct the environment. If insufficient network rights is the problem, either give the user the necessary rights, or redirect the temporary file to a more appropriate directory. 
See Also: "The Runtime Environment" chapter of 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