Error 5 Mismatching text pointers.
The pointer for the text in the .TXX file does not correspond with the cursor position pointer within the text field on the screen. DataPerfect has no way of knowing which pointer is correct. In most cases this can be corrected by exiting DataPerfect and re-entering. Exporting and importing data should eliminate the error if exiting does not.

Error 6 Buffer error while saving text.
There may be a problem in the text editor. The data should be exported and imported.

Error 7 Sequence error while saving text.
There may be a problem in the text editor. You should export and import the data. If this error occurred during a report execution, you may also need to run DPEXP/DPIMP.

Error 10 Overlay depth error.
A formula has been created that goes into a infinite loop. Recursive Keep-a-Totals may also cause this.

Error 11 Error reading overlay file.
The DP.OVL file should be re-copied from the original disks.

Error 12 Overlay calling error.
Running Dpexp and DpImp may correct this problem.

Error 51 Indexing error.
One or more index block pointers are corrupted. This may be caused by running mixed version of DP. Regenerate indexes. You may need to delete or rename the .IND file.

Error 101 Too many temporary blocks.
Too many panels with too much complexity. Simplify panels/formulas.

Error 102 Reference to deleted block.
In some cases just exiting out of DP and re-entering will solve the problem. You may want to regenerate the indexes. If this error is preceded by error 102, it could be caused by a prompt for a report variable with a multi-lined text field format. If so, delete .IND file, re-enter database and delete the prompt. Errors #197 & #102 are caused when creating a prompt for a report variable and the user tells DataPerfect that the field format is a multi-lined text field. Error #197 then #102 will appear when the report is run for the first time. The user will be unable to re-enter the database and will receive the error #102. This problem can be corrected by deleting the .IND file, reindexing the database, and removing the prompt. If you do not remove the prompt, this problem will reappear when the report is run again.

Error 103 Reference to illegal block number.
This is a stack error. You should regenerate your indexes. You may need to delete the .IND File. Could be caused by insufficient rights in the directory the .TMP files are being sent to. This error can also be caused by references to deleted panels, links, fields etc... These reference can be in reports, formulas, link key-field lists, etc....

Error 104 Temporary work space size exceeded.
Too many panels with too much complexity. Simplify panels/formulas. Using the /L startup option forces DP to hold only 2 panels in memory instead of up to 6, this will leave more memory for complex panels/formulas. Flagging the database files Non-Sharable can also cause this error.

Error 105 Error allocating temporary block.
Try deleting any temporary files. Check to see if there is ample disk space.

Error 111Too many files.

Error 113 Error writing to file(s). Network or disk error.
Check to see if there is ample disk space. Check network disk space limitations. Can be cause by losing network connection. Flagging the .STR file Read-Only can cause this error. If running under Shell 3.1 (network), try putting "TASK MODE = 4" in SHELL.CFG file.

Error 114 Error reading file(s).
If this error occurs for the .TXX file, most likely the .TXX file has gotten out of sequence. You should export all data form the database, delete the .TXX .IND and all data files, and import the data. Error messages encountered during export can be ignored except to note where the bad text is in the data. If this error occurs for the .IND file, delete the .IND file and regenerate the indexes. If this error occurs in a panel file, you will probably have to use a backup copy of the data (preferably in exported form). You may be able to export the data and re-enter missing records.

Error 115 Error extending a file.
Network or disk error. Check to see if there is ample disk space. Try deleting any temporary files. Check network rights, network space limitations, and limits of directory entries.

Error 116 Not enough directory blocks.
Could be a Network or disk error. Possibly because there are already too many files saved in this directory or disk. Check to see if the database files are in the root directory, or if the network space is limited. You may want to try reformatting the disk, or running CHKDSK. Try putting the database on another disk.

Error 117 Attempt to open bad control block.
The .STR file is corrupt. The .STR file could have been modified in an editor, or has become corrupted from some other source (bad disk sector, power failure during write, gremlins, etc...)

Error 118 Illegal read of record 0.
The .STR file may be corrupt. The .STR file could have been modified in an editor, or become corrupted from another source. This could also be caused by flagging one of the database files Non-Sharable.

Error 119 Illegal write of record 0.
The .STR file is corrupt. The .STR file could have been modified in an editor, or become corrupted from another source.

Error 120 Attempt to delete .STR file.
The .STR file could have been modified in an editor, or become corrupted from another source. They will need to use a back up of the database or redefine it.

Error 121 Attempt to read beyond end of file.
This error can be caused by many things. If this error is received in conjunction with another error(s), the other error(s) most likely are the real problem. If this error is received all by its self, it could be one of the following: Formulas that return values that are of a different type than the field will accept. Links that are defined incorrectly. Corruption in the .STR file, or garbage anywhere, visible or not. Try deleting .TMP files. Try deleting/renaming .IND file. Try running DPEXP/IMP. If the corruption is in a panel definition, DPO with the /F startup option may fix it.

Error 122 Record not found in index.
Most likely means that non-unique records exist in the panel (duplicate records are not in the index.) This can be caused if the indexes were modified and not regenerated. Regenerate first--if error displays again, edit and modify the indexes. If error persists you may need to delete the index(s) and recreate it, or, export the data, delete the panel file, and re-import. This can also be cased be having more than 80 fields in a panel (versions prior to 09/01/93.) Keep-a-totals my influence this.

Error 133 Attempt to insert duplicate index key.
DataPerfect created what it thinks to be a unique key, but experienced a collision when trying to insert it (this is different than a 122 error.)

If the database is on a network, wait a few seconds and try re-saving. If the error persists, regenerate the indexes. If this error occurs during an import, try deleting the panel file at DOS and re-importing.

Additional notes on this error from Lew Bastian. First of all, whenever an error (like the error 133) is triggered, it means that something has happened that is "impossible" as far as DP is concerned. Often it is a symptom of a programming error [bug] deep within DP (that will be hard to find.) Sometimes such an error can be triggered by the user, and sometimes a hardware failure is involved.

The error 133 you report was last seen several years ago, and the bug that caused it to appear was fixed. I believe the context for a 133 error has not changed since version 2.2.

When saving a record in create mode, DP first locks the database, then it goes through the panel indexes one by one to see if the record keys can be inserted -- but no insertions are actually made. (If this step fails you get the "duplicate record" message.)

Assuming success, the record is added, and then the keys are inserted into the indexes -- and this should never fail because the check has been made and the database has remained locked. However, a test is made for failure, and it is this failure that causes the 133 error. Note that, in the current version, the record has been added, so index regeneration for the panel will include that record if it was unique, but it will give the (false) message that one or more indexes need redefinition if the record is not unique. In version 2.2 there was a fairly rare error during index key deletion that resulted in index structure errors that could lead to an error 133. That particular error was fixed three years ago, so you need to upgrade your version to avoid that error.

Furthermore, I believe that in version 2.2 the record addition was cached, so it may not have been written -- that would explain the blank record you are seeing. The changes between the version you are using and the current version are substantial, but when you upgrade you should only have to examine the reports to make sure that page breaks occur at the same places -- and usually they will.

Error 151 Reference to non-text file.
The .TXX file that DataPerfect is trying to read is either corrupt or not a .TXX file. Restore from a backup. If there is no backup, the .TXX file can be deleted, but all data in every multi-line text field in the database will be lost.

Error 152 Reference to file 0.
The .TXX file that DataPerfect is trying to read is either corrupt or not a .TXX file. Restore from a backup. If there is no backup, the .TXX file can be deleted, but all data in every multi-line text field in the database will be lost.

Error 153 Attempt to write text to text block 0.
The .TXX file that DataPerfect is trying to write to is either corrupt or not a .TXX file. Restore from a backup. If there is no backup, the .TXX file can be deleted, but all data in every multi-line text field in the database will be lost.

Error 154 Attempt to read block 0 as text.
The file DataPerfect is trying to read is corrupt or not a valid format. Restore from backup. If there is no backup, try deleting the .IND file, exporting all data, deleting panel files and .TXX file, importing data.

Error 155 Attempt to write text block beyond file end.
Most probably the .TXX file has gotten out of sequence. Restore from backup. If there is no backup, try exporting all data, deleting data and .TXX file, importing all data.

Error 171 Reference to data type 0.
The structure file has been corrupted. This could be caused by modifying the .STR file in an editor, or making invalid changes to the .STE file, and running DPIMP. Restore from backup.

Error 172 Reference to illegal data type.
The structure file has been corrupted. This could be caused by modifying the .STR file in an editor, or making invalid changes to the .STE file, and running DPIMP. Restore from backup.

Error 173 Attempt to write data to un-allocated record.
The .STR file is corrupted or has an error in it's free space array. Try running DPEXP/DPIMP. This could be caused by modifying the .STR file in an editor, or making invalid changes to the .STE file, and running DPIMP. Restore from backup.

Error 183 Illegal picture encountered.
Can mean that corruption was encountered in any part of the database. If it occurred during a report execution, check for fields/indexes/RV's in the report that have since been deleted. Either redefine the report or delete the references to information that has already been deleted. This error can be caused Incorrect or corrupted formulas. If this error occurs when trying to enter a panel, the corruption is probably in the panel text. If running DPEXP/DPIMP does not remove it, editing the .STE file, or deleting and rebuilding the panel may be required. If this occurs during an import, export data from that panel and delete panel file, then re-try import.

Error 184 Reference to nonexistent index root.
An index that was used in a link or report or lookup etc. has been deleted or has been corrupted. The indexes will probably need to be regenerated. The index may need to be deleted and redefined if regenerating does not work. If the index has been deleted, the link/report/lookup will need to be modified or redefined to reference an existing index.

Error 187 Bad panel structure (target path).
A reference to a deleted panel has been found. This could happen in a subreport, report, formula, link etc. Re-select the field, redefine subreport, etc....

Error 188 Undefined search type.
The .STR file is corrupted. Could be caused also by creating search conditions in a report then deleting the fields used in the search. Reset search conditions. Running DPEXP/DPIMP may also be necessary.

Error 190 Reference to un-allocated temporary record.

Error 191 Attempted use of non-text field as text.
A non-text value is being treated as text. Could be a formula on a text field that returns a value in a numeric format, G, N, etc.... Can also be caused if a text field was selected in a report and then the format in the panel was changed to not be a text field.

Error 192 Illegal element in formula.
This may be caused if a database was created using a newer version of DataPerfect (using new features) and then the database is used on an older version of DataPerfect where those new features have not been implemented. May also be the result of corruption.

Error 193 Illegal pointer type in formula.
The formula contains a pointer to a field or function that returns the wrong data type. (i.e. a string where a number is expected, or visa versa.)

Error 196 Error in .STR file.

Error 197 Illegal type in report definition.,br> This error occurs almost exclusively when running reports. This can be caused by invalid modifications to the .STR or .STE files in an editor. Could be caused by using "create record through link" in a report and then deleting the link. Could be caused by printing an RV with a numeric value using an alphanumeric format (or visa versa), selecting a field in a report then modifying the format in the report. If error 102 follows this error, it could be caused by a prompt for a report variable with a multi-lined text field format. If so, delete .IND file, re-enter database and delete the prompt. See additional notes at error #102.

Error 198 Illegal panel/file type.
File repositioning error during lookup, search or multi-remove. Try regenerating indexes. Try running DPEXP/DPIMP. The index may need to be deleted and recreated.

Error 199 File repositioning error.
This is the same type of error as 121 except it is manifest during search, global delete, lookup, or multi-remove.

Error 200 Internal Error .
This error can be caused by links containing fields with mismatching formats. Could be caused by importing a secondary merge file that contains Bold or underline codes. This may also be caused by importing 5.0/5.1/5.2/6.0 secondary merge files into older versions of DataPerfect than support that WP version. In older versions of DataPerfect (before the Hot-Table was implemented) this error could be caused by too many formulas that referenced other fields with formulas.

Error 303 Invalid field reference.
A lookup contains a field that no longer exists.

Error 55x Erroneous index block structure.
Any error that begins with 55 means that the index has gotten out of order. The indexes need to be regenerated. The .IND file may also need to be deleted. This could also mean the index key size has been exceeded, look for indexes that contain large number of fields or multi-line text fields.