TECH TIP
CODE BASE ERROR MESSAGES

Information on CodeBase Error Messages for the Reporting to the MAX

Codebase is a Database Tool used by Reporting to the MAX including Point of Sale and Non-profit Versions to access database files to store or retrieve information. Codebase errors are generated when there is a problem reading or writing to a CMS database file. The error numbers below correspond to the number that appears in the first line of a Codebase error, not the numbers that appear below.

Error Number: -1
Possible Cause:
A previous Codebase error causes Codebase function calls to return -1.
Explanation:
When a call to a Codebase function fails, CODE4.errorCode is set to a particular error code. These codes may be found in the 'Error Codes' Appendix of the Reference Guide. When the error code is set to a number less than 0, each subsequent Codebase function will simply return a -1, without executing the function. This is done for safety purposes.
Notes: This error occurs when Codebase cannot return a valid error code because of some problem. This usually occurs when the file is corrupted or network permissions on a file are changed while the file is already open and in use by CMS.
Solution:
Exit CMS, restart the workstation, log back onto network. If the problem was permissions, you will get a different error message, because the file is no longer available. If you get a Codebase 200, repair or Restore from Backup. [see the -200 error]

Error Number: -20
Description:
Unable to create file
Possible Cause #1:
The specified file already exists.
By default, when Codebase attempts to create a data, index, or memo file, it does not overwrite any existing file of the same name, and instead returns an error. This default behavior is specified by the value contained in the CODE4.safety member variable, which is set to 1 by default. To create a file if one by the same name already exists, set CODE4.safety to 0. See the example for CODE4.safety in the Reference Guide.
Possible Cause #2:
Codebase ran out of valid file handles.
Explanation:
By default, only 20 file handles are available to 16-bit applications at any one time, under Windows 95/98. Windows NT/2000 are set up to either 20 or 40 by default.
Solution: Check file handles in CONFIG.SYS (CONFIG.NT in Win NT, 2000, XP) and increase to 150 or 250, using standard CMS system configuration instructions found in the CMS Installation Tips document as a guide.
Notes: Please use the standard numbers given for file handles. Some NT Operating Systems will not work with a setting of 255; Microsoft designed Windows NT4.0 to accept a setting of 254 or less.

Error Number: -30
Description:
Determining File Length
Possible Cause:
Codebase ran out of valid file handles.
Solution:
More file handles must be assigned to allow Codebase to manage files properly
[See error -20]

Error Number: -60, -70
Description:
Error opening or reading a file
Possible Cause:
Insufficient network rights or permissions to open or read the file.
Solution: With Windows NT/2000 Server: check the permissions set on the share at the server, either reset permissions to allow access to all users or grant permissions with FULL CONTROL to the group(s) and/or users who are having trouble accessing CMS data files.

Error Number: -310
Description:
Index Error
Possible Cause:
Damaged index tag data in the .MDX index file
Explanation:
Index file is corrupt.
Solution:
Index file can be repaired with the DBFix and FileFix utilities found in the CMS program folder if the data file still contains a header identifier). If the file is seriously corrupt, try correcting with Visual DBase (it can rebuild a data file with a damaged header.) If multiple files are affected and these methods don't work, it is best to restore from backup.

Error Number: -910
Description:
Unexpected Information or Database file already open
Possible Cause:
The file that is being opened has been opened previously.
Explanation:
Database structure error. Either a blank record has been appended to the data file or the fields in the existing data file do not match the file structure being read or written to.
Solution:
If a blank record exists at the bottom of the file, delete it and correct the condition that caused it (i.e., duplicate invoice or check number in AP, BR.) If there is no blank and/or no filename is listed on the error, get all users out of CMS and force a Windows to Windows Conversion (Win2Win) at the server machine. If the problem is not corrected by the Win2Win Conversion (or reappears on the same file after this file is reindexed,) then the main dictionary file (DEFAULT.MDB) may be corrupt. To fix a corrupted main dictionary file, rename the DEFAULT.MDB in the CMS program folder and reinstall from CD and then install the current service pack. [...Or one can rename the CMSWIN folder, create a clean install on the current service pack and move the data over from the old install.] The assistance of CMS Technical Support may be required to successfully correct a problem related to a corrupt main dictionary file.

Error Number: -930, 935, etc
Description:
Unexpected Parameter
Possible Cause:
A call to a Codebase function included a parameter that was not valid.
Explanation:
This error almost always occurs after another Codebase error, like a -910 error.
Solution:
Take note of the first Codebase error message received, click through all of the other errors that may follow and ignore them. If a -930 or -935 error occurs as the first error message, force a Win2Win Conversion [see error -910]