DFIC Error 54 - Client ID/Trust ID Not Defined

Last reviewed: 08/08/2002
Article ID: R10611

The information in this article applies to:

• Tabs3 Version 10 & 11
• TAS Version 10 & 11
• PracticeMaster Version 10 & 11

SUMMARY

This error indicates that a record has been encountered with a Client ID/Trust ID that does not exist.

RESOLUTION

It is possible to correct this error; however, depending on the severity of the error, there is the possibility that the error cannot be corrected thereby requiring that data be restored from a backup.

The procedures used to correct this error depend on the file the error is in. Use the following procedures to attempt to correct this error with the following exceptions:
If the error is in the Tabs3 Payment Allocation (Pymt Alloc) or the Client Ledger file (Ledger), use the procedures under Error in Tabs3 Payment Allocation or Ledger File.  If the error is in the Tabs3 Pre-Bill Tracking file (Stmt Track), use the procedure under Error in Tabs3 Pre-Bill Tracking File. 

1. Make a temporary backup. Do not overwrite a current backup.
2. Add a new client/trust record using the Client ID/Trust ID shown on the Data File Integrity Check Error Report. (Note: You will only be allowed to add the client/trust account if it conforms to the current Key Type, Decimal Place and is not zero.)
3. Run the Data File Integrity Check program and correct any errors that occur. (There have been cases where, after adding the record, the Data File Integrity Check will return an Error 26.) Proceed only when the Data File Integrity Check reports no errors.
4. If the Client ID/Trust ID is invalid, delete the new Client ID/Trust ID. Deleting the client/trust account record automatically removes any associated records for the client/trust account.
5. If the Client ID/Trust ID is valid, all associated records will now be accessible.
6. Rerun the Data File Integrity Check program.
7. If the Data File Integrity Check still indicates errors, you must restore the appropriate program's data files from a backup.
8. If there are no errors during the Data File Integrity Check, you may resume using the software.

PracticeMaster Note:  If the client number cannot be reentered due to an invalid Key Type or Decimal Place, when previewing the Data File Integrity Check Error Report, use the built-in drill-down capabilities to quickly ac cess the record. When you mouse over an error on the report, it will be highlighted in yellow. Clicking the error will open an Editor window for that record allowing you to delete the record.

Error in Tabs3 Payment Allocation or Ledger File

If the error 54 is in the Pymt Alloc or Ledger file, use the following instructions to attempt to fix the error.

1. Make a temporary backup. Do not overwrite a current backup.
2. Add a new client record using the Client ID shown on the Data File Integrity Check Error Report. (Note: You will only be allowed to add the client if it conforms to the current Key Type, Decimal Place and is not zero.)
3. Use the Edit Client Ledger program to add enough client ledger records to create a ledger record with the Reference # listed on the Data File Integrity Check Error Report. Based on the sample Data File Integrity Check Error Report above, 10 ledger records would have to be added to create Ref # 10.
4. Run the Data File Integrity Check. Continue only if there are no errors.
5. Delete the new client.
6. Rerun the Data File Integrity Check program.
7. If the Data File Integrity Check still indicates errors, you must restore your Tabs3 data files from a backup.
8. If there are no errors during the Data File Integrity Check, you may resume using the software.

Alternate Solution:

1. Make a temporary backup. Do not overwrite a current backup.
2. Add a new client record using the Client ID shown on the Data File Integrity Check Error Report. (Note: You will only be allowed to add the client if it conforms to the current Key Type, Decimal Place and is not zero.)
3. In the Edit Client Ledger program, enter the first Client ID and reference number from the Data File Integrity Check Error Report. Delete the ledger record by clicking the Delete icon on the toolbar. Do not adjust the Receipt Allocation when prompted.
4. After all ledger records from the Data File Integrity Check Error Report have been deleted, run the Data File Integrity Check to verify the errors have been eliminated.
5. Delete the new client and run the Data File Integrity Check program again.
6. If the Data File Integrity Check still indicates errors, you must restore your Tabs3 data files from a backup.
7. If there are no errors during the Data File Integrity Check, you may resume using the software.

Error in Tabs3 Pre-Bill Tracking File

1. Make a temporary backup. Do not overwrite a current backup.
2. Add a new client record for each error 54 listed on the Data File Integrity Check Error Report.  Use the Client ID shown. (Note: You will only be allowed to add the client if it conforms to the current Key Type, Decimal Place and is not zero.)
3. Open the Pre-Bill Tracking screen (Statements|Pre-Bill Tracking) and delete the record for each of these added clients.
4. Delete these client records again and run the Data File Integrity Check program.
5. If the Data File Integrity Check still indicates errors, you must either restore your Tabs3 data files from a backup or call STI's Technical Support Department.
6. If there are no errors during the Data File Integrity Check, you may resume using the software.

REFERENCES

• 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-2003 Software Technology, Inc.   All rights reserved.
Knowledge Base:   http://support.Tabs3.com
Web Site:   http://www.Tabs3.com