DFIC Error 54 - Client ID/Trust ID Not Defined
Last reviewed: 02/19/2009
Article ID: R10611
The information in this article applies to:
- Tabs3 Billing Software Version 15, 14 & 12
- Tabs3 Trust Accounting Software (TAS) Version 15, 14 & 12
- PracticeMaster Version 15, 14 & 12
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:
- Make a temporary backup. Do not overwrite a current backup.
- 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.)
- 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.
- 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.
- If the Client ID/Trust ID is valid, all associated records will now be accessible.
- Rerun the Data File Integrity Check program.
- 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.
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 |
|
- Make a temporary backup. Do not overwrite a current backup.
- 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.)
- 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.
- Run the Data File Integrity Check. Continue only if there are no errors.
- Delete the new client.
- Rerun the Data File Integrity Check program to confirm that the error(s) have been corrected.
- If the Data File Integrity Check still indicates errors, you must restore your Tabs3
data files from a backup.
Alternate Solution:
- Make a temporary backup. Do not overwrite a current backup.
- 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.)
- 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.
- 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.
- Delete the new client and run the Data File Integrity Check program again to confirm that
the error(s) have been corrected.
- If the Data File Integrity Check still indicates errors, you must restore your Tabs3
data files from a backup.
- Make a temporary backup. Do not overwrite a current backup.
- 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.)
- Open the Pre-Bill Tracking screen (Statements | Pre-Bill Tracking)
and delete the record for each of these added clients.
- 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.
- 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
- 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-2010 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