DFIC Error 26 - Reference Number is Too Large

Last reviewed: 12/12/2011
Article ID: R10608

The information in this article applies to:

Tabs3 Billing Software Version 16, 15, 14 & 12
Tabs3 Remote Entry Software Version 16, 15, 14 & 12
Tabs3 Trust Accounting Software (TAS) Version 16, 15, 14 & 12
Tabs3 Accounts Payable Software (APS) Version 16, 15, 14 & 12

SUMMARY

This error indicates that an invalid reference number has been encountered. Depending on which error the file is in, it may or may not be possible to resolve this error without restoring from a backup. The resolution of these errors depends on the file in which the error occurs:

Data Entry File (T3FEE, T3COST, T3PYMT, T3FUND, RMTFEE, RMTCOST, T4TRANS, or A3INVOIC)
Tabs3 Ledger File (T3LEDGER)
Tabs3 Statement Files (STMT DETAIL, STM DET ALLOC, or LEDGER ALLOC)

Note: This error is not reported when running the Data File Integrity Check with the Read Only check box selected.

RESOLUTION

If the error 26 is in a data entry file

There are two methods for correcting error 26 in most files. You may be able to resolve this error by reindexing the file shown on the Data File Integrity Check Error Report with the Compact option selected. However, if the any of the following files is compacted, the reference numbers of transactions in the file may change:

Tabs3	Fee file (T3FEE)
	Cost file (T3COST)
	Payment file (T3PYMT)
	Client Funds file (T3FUND)
Tabs3 Remote	Fee file (RMTFEE)
Tabs3 Remote	Cost file (RMTCOST)
TAS	Transaction file (T4TRANS)
APS	Invoice file (A3INVOIC)

In addition, if the Tabs3 Ledger file (T3LEDGER) is compacted, the reference numbers shown on the client ledger records may change.

To compact the affected file:

Make a temporary backup. Do not overwrite a current backup.
Access the Reindex Files program (Utilities | Reindex Files).
Click Select Files and select the file shown on the Error Report from the Select Files window.
Select the Compact Selected Files check box.
Click OK to reindex the selected file.
If the reindex process does not complete successfully, you must restore from a backup. If the reindex process successfully completes, rerun the Data File Integrity Check program to confirm that the error has been eliminated.
If the Data File Integrity Check still indicates an error 26, you must restore from a backup.

Optionally, you can attempt to delete the entry shown on the Data File Integrity Check Error Report without changing the reference numbers of other records. This method cannot be used if the error is in the Tabs3 Ledger file (T3LEDGER).

To delete the affected record:

Make a temporary backup. Do not overwrite a current backup.
Open the file shown on the Data File Integrity Check Error Report.
Select the record shown on the Data File Integrity Check Error Report.
Note the information of this record, as it will need to be re-entered after the error is eliminated.
Click the Delete button on the toolbar.
Rerun the Data File Integrity Check program to confirm that the error has been eliminated. If the error has been eliminated, re-enter the record as noted above.
If the Data File Integrity Check still indicates an error 26, you must restore from a backup.

If the error 26 is in the following Tabs3 files

Tabs3	Statement Detail (Stmt Detail)
	Statement Detail Allocation (Stm Det Alloc)
	Ledger Allocation (Ledger Alloc)

An error 26 in the Statement Detail, Statement Detail Allocation, or Ledger Allocation file indicates an invalid or corrupted reference number has been encountered. Compacting the Ledger file (see above) may resolve an error 26 in the Statement Detail file. However if the errors persist or new errors are generated by the DFIC, or the error 26 is in the Statement Detail Allocation or Ledger Allocation files, you will need to do one of the following:

Restore from a backup made prior to the error occurring.
Send the data to Software Technology, Inc. to be fixed. There will be a charge for data analysis and/or repair.

If you restore all Tabs3 data files, any tasks performed after the backup was made must be performed again.

REFERENCES

KB Article R10102 - How Reindex Data Files Affects Your Data
KB Article R10167 - Data File Integrity Check Errors in Verification Files
KB Article R10686 - Using the Built-In Backup Program Without Overwriting an Existing Backup

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

© 1999-2012 Software Technology, Inc. All rights reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol () are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base: http://support.Tabs3.com
Web Site: http://www.Tabs3.com