DFIC Error 54 - Client ID/Trust ID Not Defined

Last reviewed: 02/19/2009
Article ID: R10611

The information in this article applies to:

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 a possibility that it 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:

  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 and Decimal Place and it 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.

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 access 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 Payment Allocation file (Pymt Alloc) or Client Ledger file (Ledger) and you are running Tabs3 Version 12.2 or earlier, use the following procedures to attempt to fix the error. If you are running Tabs3 Version 14 or later, you must restore your Tabs3 data files from a backup.

Data File Integrity Check Error Report

Count

Error Code

File Name

Location

Desc.

Seq No

1

54

Pymt Alloc

Client 622.00 Ref 10 Type 2

Client ID

9387

1

54

Pymt Alloc

Client 622.00 Ref 10 Type 1003

Client ID

9386

  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 and Decimal Place and it 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 to confirm that the error(s) have been corrected.
  7. If the Data File Integrity Check still indicates errors, you must restore your Tabs3 data files from a backup.

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 and Decimal Place and it 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 button 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 to confirm that the error(s) have been corrected.
  6. If the Data File Integrity Check still indicates errors, you must restore your Tabs3 data files from a backup.

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 and Decimal Place and it 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 the client records added in step 2 and run the Data File Integrity Check program to confirm that the error(s) have been corrected.
  5. If the Data File Integrity Check still indicates errors, you must either restore your Tabs3 data files from a backup or call our Technical Support Department.

REFERENCES


© 1999-2010 Software Technology, Inc.   All rights reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (The "Pinwheel" symbol is a Registered Trademark of Software Technology, Inc.) 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