DFIC Error 51 - Invalid Client ID/Trust ID

Last reviewed: 08/02/2011
Article ID: R10609

The information in this article applies to:

• Tabs3 Billing Software Version 16, 15, 14 & 12
• Tabs3 Remote Entry Software Version 16, 15, 14 & 12
• PracticeMaster Version 16, 15, 14 & 12
• Tabs3 Trust Accounting Software (TAS) Version 16, 15, 14 & 12

SUMMARY

This error indicates that a record has been encountered that contains a Client ID/Trust ID with an invalid character. The best solution is to restore from a backup. However, if restoring is not an option, you may be able to eliminate this error.

RESOLUTION

In a Tabs3 Client Rate Table

1. Preview a Client Rate Report (Reports | Client | Client Rate Report). Make sure the Fee Rate Table and Cost Rate Table check boxes are selected on the Options tab. (If using Version 10, make sure the Rate Table check box is selected on the Options tab.)
2. Look for the message "Shared client rate table not found for client xxxx". (Tip: Click the Search button and search for the text not found.)
3. Once you have identified the client(s) without a shared client rate table, open that client in the Client Information program (File | Open | Client).
4. Click the Rates tab and then click the Fee Rate Table button (or Cost Rate Table button if the error is in the cost table).
5. Click either Shared or Custom.
6. Save your changes and close the Client Information window.
7. Rerun the Data File Integrity Check program.

In Tabs3, TAS or PracticeMaster

A3T3COST

After updating to Version 14.2, it is possible to receive multiple Error 51s in the A3T3COST file. The Data File Integrity Check (DFIC) has been designed to automatically correct these errors when run with the Read Only option cleared. If these errors occur, run the DFIC again to verify that the errors have been corrected.

Otherwise, the following procedure may be used to attempt to resolve an Error 51.

1. Make a temporary backup (do not overwrite a current backup).
2. Access the Reindex Files program (Utilities | Reindex Files).
3. Click Select Files and select the file shown on the Error Report from the Select Files window.
4. Select the Delete records that contain errors check box.
5. Click OK to reindex the selected file. This process will delete the records that have the invalid Client ID/Trust ID.
6. If this process successfully completes, you will be able to print an Error Report showing the deleted record.
7. Rerun the Data File Integrity Check program.
8. If the integrity check still indicates errors, you must restore the appropriate program's data files from a backup.
9. If the Data File Integrity Check completes with no errors, the errors have been eliminated by deletion of the corrupted records. You can reenter the corrupted records shown on the Reindex Files Error Report.

Client ID

After updating to Version 16, it is possible to receive Error 51s in the Client file when using an Alpha or Mixed Key Type. Characters from the IBM extended character set can be used in the client names and other fields. These are characters assigned to ASCII values between decimal 128 and 255, such as the ñ character. However, extended characters can no longer be used in the Client ID field. Additional information regarding extended characters can be found in R11066, Extended ASCII Characters.

If you have extended characters in the Client ID field, you must renumber the client.

1. Make a temporary backup (do not overwrite a current backup).
2. Access the Renumber Client program (Maintenance | Renumber | Client).
3. Select the Old Client ID shown on the Error Report.
4. Enter a New Client ID that does not contain extended characters.
5. Click OK to renumber the client.
6. Rerun the Data File Integrity Check program.
7. If the integrity check still indicates errors, you must restore the appropriate program's data files from a backup.

In PracticeMaster

The following alternative resolutions can be used for PracticeMaster if the above resolution did not work:

• Drill down from the error report, delete the record and re-enter it. Rerun the Data File Integrity Check to make sure the error was removed.
• If you are unable to correct the error by drilling down and editing, and restoring from a backup is not an option, as a last resort, it may be possible to salvage the data by exporting, erasing and reimporting the data. The import process will reject the record(s) containing invalid Client IDs, thereby eliminating them from the Client file. For more information and instructions on this procedure, please refer to KB Article R10522, "Rebuilding PracticeMaster Data".

In Tabs3 Remote

In Tabs3 Remote, this error can occur in either the remote data files or the optional validation files.

• If you are using the optional Tabs3 validation files, this error will occur if the Tabs3 Key Type is different than the Key Type specified in Tabs3 Remote or if the Tabs3 Decimal Places (Matter Length prior to version 10.6) is greater than the Decimal Places specified in Tabs3 Remote. Compare the Key Types and Decimal Places in both programs. If they are different, change the Remote Key Type or Decimal Places to match the Key Type or Decimal Places in Tabs3. Rerun the Data File Integrity Check.
• If the error is in the optional validation files, simply recreate the optional validation files in Tabs3 and transfer them to the remote data directory.
• If the error is in the remote data files, it cannot be corrected. If possible, restore from a backup. Depending on the position of the record in the data file and the extent of the problem, it is possible to merge the remote data files into Tabs3 and have the transactions without this error successfully merged but receive a reject code for the transaction record(s) with this error.

REFERENCES

• KB Article R10167 - Data File Integrity Check Errors in Verification Files
• KB Article R10102 - How Reindex Data Files Affects Your Data
• 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