[Previous] 

37    Too many symbols in symbol table
This error occurs with an application linked with Exospace. The application will terminate immediately upon start up. This is caused by CODE GENERATORS that generate an excessive amount of symbols. 
Action: Some suggestions to resolve the problem are: 
1) Decrease that amount and/or reuse symbols, declare as local. 
2) List .PRGs in .CLP files to compile fewer and larger .OBJ files. 
3) Some visitors have reported that the problem went away after switching to Blinker or rebuilding the entire application and libraries 
See Also: "Compiling" chapter in the Programming and Utilities Guide and the "CA-Clipper Technical Specifications" appendix. 

92    SORT/INDEX ON Error
The system is unable to create a temporary file during a SORT or INDEX operation. This can occur for one of the following reasons: 
1) No disk space; 
2) Disk is write-protected; 
3) No more directory entries; or 
4) The file already exists and is read-only. 
5) There are not enough file handles available. 
6) If running under Windows 95, try using an updated network driver or client. Try switching between the Microsoft "Client for NetWare Networks" and the Novell client in the Network applet in the Control Panel. Check both the Microsoft and Novell websites for the latest updates and 32-bit clients. 

331    String/Array buffer/memory overflow
In the worst case, this error will occur when slightly over a megabyte of strings and/or arrays are in use; the best case is in excess of 16 megabytes. Probably the most common cause of this error is the declaration of extremely large arrays (e.g., local aArray[500][300]). Every array element requires memory to store (even if its value is NIL). The number of array elements in an array is determined by multiplying the number of elements in every dimension and adding the sum of all dimensions except for the last. For example, a 500 by 300 array has (500 x 300) + 500, or 150,500 elements. As every array element in CA-Clipper requires 14 bytes, this amounts to 150,500 x 14 or 2,107,000 bytes -- well in excess of one megabyte and, therefore, potentially dangerous. 
Action: Reduce the size and/or number of strings and arrays that are active at any one time. Declare as many string variables and arrays LOCAL as possible. 
Note: There is no benefit gained by reusing arrays. CA-Clipper is much more efficient when strings and arrays are thrown away and rebuilt often rather than kept around unnecessarily for long periods. 

332    String/Array memory overflow
The maximum capacity of the Segment Virtual Object Store (SVOS) system has been exceeded. Because of the dynamic nature of SVOS, it is impossible to state exactly when this error will occur (see the Release Notes database in Norton Guides, "5.x Notes" under "Runtime Memory Management"). In the worst case, this error will occur when slightly over a megabyte of strings and/or arrays are in use; the best case is in excess of 16 megabytes. Probably the most common cause of this error is the declaration of extremely large arrays (e.g., local aArray[500][300]). Every array element requires memory to store (even if its value is NIL). The number of array elements in an array is determined by multiplying the number of elements in every dimension and adding the sum of all dimensions except for the last. For example, a 500 by 300 array has (500 x 300) + 500, or 150,500, elements. As every array element in CA-Clipper requires 14 bytes, this amounts to 150,500 x 14, or 2,107,000 bytes -- well in excess of one megabyte and, therefore, potentially dangerous. 
Action: Reduce the size and/or number of strings and arrays that are active at any one time. Declare as many string variables and arrays LOCAL as possible. 
Note: There is no benefit gained by reusing arrays. CA-Clipper is much more efficient when strings and arrays are thrown away and rebuilt often rather than kept around unnecessarily for long durations. 

335    String/Array invalid pointer
This results from an error accessing the memory address for a string value during an element assignment while declaring a large multidimensional array. 
Action: Try declaring an empty array and then build the array using aadd(). Check string assignments for a NULL character. 

336    String/Array memory overflow
This results from trying to a declare a large multidimensional array. 
Action: Try declaring an empty array, and then build the array using aadd(). 

340    Too many Extend locks
This error has occurred in a CA-Clipper 5.2e application that uses the Faxual II fax library. The error might indicate that there is insufficient virtual memory for the needs of the program, or that there is not enough room to store the memory pointers. 
Action: Increase the amount of virtual memory. Alternatively, increase available conventional memory or reduce the amount of virtual memory, because more VM means more conventional memory is needed to manage the VM pointers. 

415    Cannot open overlay file
This error occurs when a CA-Clipper application cannot find or cannot open an overlay file. Overlay files include executable (.EXE) files (in the case of dynamic overlays), pre-linked library (.PLL) files, and static overlay (.OVL) files. 
Action: Probably the most common cause of this error is insufficient file handles available to the CA-Clipper application. The first step in trying to solve this problem is to increase the number of file handles available to the application. Refer to "File and Buffers" section in the Runtime Environment chapter of the Programming and Utilities book. 
If insufficient file handles is not the problem, it is possible that the CA-Clipper application cannot find the file it is trying to open. Refer to "Specifying the Location of Executable Files" section in the Runtime Environment chapter of the Programming and Utilities book. It is possible that another file of the same name as the executable is in the DOS path and is being searched for the overlay. Try renaming the executable. 
The problem might involve specifying an object filename longer than 8 characters. The extra characters are ignored during file access, so the link works, but the EXE has the extra characters in its reference to itself for VMM and dynamic code swapping. When you run the application, it fails to load another part of itself because the internal file name is invalid. 

416    Read error on dynamic page file (overlay)
This error indicates that the runtime manager could not READ from overlay. 
Action: Some suggestions to resolve the problem are: 
1) Make sure you are not deleting or using fclose() on any file handles that you did not specifically create. 
2) If you are on a network, make sure that the server did not lock up. Also make sure that the workstation has not been disconnected. Check the validity of the network cards, cabling, drivers, etc. 
3) Increase the number of file handles available to the application. 
4) Check that the application's EXE drive and directory are still valid. 
5) Make sure the .EXE is marked READONLY (the overlay manager always opens page files SHARED and READONLY). 
6) Make sure there are no duplicates of the .EXE file available through any MAP, PATH, or SEARCH drive, in case the overlay manager is somehow getting hold of another file with the same name. Erase duplicate .EXE files. 
7) Do not rename the .EXE. Recreate it with an alternative OUTPUT link command. 

520    Attempt to get value for an invalid field type.
This error may indicate a corrupted or non CA-Clipper compatible database file. 
Action: Repair the database header and field structure. 

521    Replacement of field with invalid data type.
Self-explanatory.
[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