DFIC Error 51 - Invalid Client ID/Trust ID

Last reviewed: 08/19/2002
Article ID: R10609

The information in this article applies to:

Tabs3 Version 10 & 11
Tabs3 Remote Version 10 & 11
PracticeMaster Version 10 & 11
TAS Version 10 & 11

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 Tabs3 Client Rate Table

Preview a Client Rate Report (Reports|Client|Client Rate Report).
Look for the message "Shared client rate table not found for client xxxx". (Hint: Click the Search button and search for the text not found.)
Once you have identified the client(s) without a shared client rate table, open that client in the client data entry program (File|Open|Client).
Click the Table tab.
Either select a shared table to use or select Custom.
Save your changes and close the Client window.
Rerun the Data File Integrity Check program.

In Tabs3, TAS or PracticeMaster

Make a temporary backup (do not overwrite a current backup).
Access the Reindex Files program.
Select the Reindex Specific Files option and select the file shown on the Error Report. Then select the Delete records that contain errors check box and start the Reindex Files program. This process will delete the records that have the invalid Client ID/Trust ID.
If this process successfully completes, you will be able to print an Error Report showing the deleted record.
Rerun the Data File Integrity Check program.
If the integrity check still indicates errors, you must restore the appropriate programs data files from a backup.
If there are no errors during the Data File Integrity Check, the errors have been eliminated by deletion of the corrupted records. You can reenter the corrupted records shown on the Reindex Files Error Report.

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. Re-run the Data File Integrity Check to make sure the error was removed.
If the above two methods did not eliminate the error and restoring from a backup is not an option, as a last resort, it may be possible to salvage some data by exporting the data. The Export Data program can be accessed via File Maintenance on the Utility tab. Once the data is exported, delete the CMCLIENT.DAT and CMCLIENT.IDX files and reimport the .EXP file. Refer to R10522-Rebuilding PracticeMaster V10 Data for more information.

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 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 errors are in the optional validation files, simply recreate the optional validation files 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 the Reindex Files Program 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.