The Tabs3 Billing Data File Integrity Check Error Report consists of one line of information for each error found during the Data File Integrity Check program. You can print, preview or save the report. If you are a user with manager rights, you can use the built-in drill-down capabilities when previewing the report to quickly edit certain errors. When you mouse over an error on the report, it will be highlighted in yellow. Clicking the error will open a data entry window for that record allowing you to edit it. (Note: Not all errors will have drill-down capabilities.)

The following information is shown for each error:

Count Counter showing the number of errors found.
Error Code Error code number. Use this number to look up the solution below.
Error Description Provides a description of the error that has been found.
File Name File that contains the error.
Field Indicates which field in the affected file contains the error.
Client ID Client or record with the error.
Key<Ref#> Varies depending on the file in which the error was found. Refer to the legend printed at the end of the Error Report.
Seq No Record location (for Tabs3 Support use only).

Note: If you open a data entry window but do not want to edit the record at that time, you may need to use the button to close the window if errors are present in the record.

The following contains a list of possible error codes that can occur during the Data File Integrity Check along with a description of each error. Click on the Error Code to see possible solutions.

Note: The following errors are not reported when running the Data File Integrity Check with the Limited Scan option selected: 23 (when occurring in a file other than the Client file), 26, 27, 66, and 69.

Clicking the links for the following errors will open your default Internet browser to the corresponding Knowledge Base article on the Internet.

        Code  Description of Error/Warning

2 - Index Performance Warning

10 - Invalid Character

11 - Invalid Category

14 - Invalid WIP_PYMT_SEQNO

16 - Bad Space Padding

17 - Inconsistent Record Value

19 - Virtual Out of Sync

21 - Invalid Value for Boolean Field

22 - Integer Out of Range

23 - Reference Number is Negative

24 - Statement Number is Negative

26 - Reference Number is Too Large

27 - Reference Number is Zero

51 - Invalid Client ID

52 - Invalid Date

54 - Client ID Not Defined

55 - Keys Out of Sequence

56 - Invalid Sequence Number

57 - Invalid Link

59 - Invalid Client ID in Shared Client Rate Table

60 - Split Billing Client IDs Not Equal

66 - Duplicate Mirror Sequence Number

69 - Duplicate Keys

71 - Duplicate Task Code

72 - File Structure is Corrupt (Bad DODA)

73 - File Structure is Corrupt (Bad IFIL)

74 - Missing File

80 - Invalid Transaction Code

81 - Invalid Task Based Billing Code

83 - File Must be Reindexed

84 - File Verify Error

85 - Bad Index in File

93 - Transaction Overflow

94 - Invalid Percentage in Split Billing File

95 - Invalid Timekeeper

96 - Empty Field

97 - Colon Not Allowed

98 - Invalid Hours Worked

99 - Invalid Units

112 - Missing Bill To Record

138 - Fee Comp Rule Discrepancy

139 - Invalid Email Template

145 - User ID Not Defined

147 - Location Not Defined

150 - Contact Not Defined

174 - Invalid Syntax in Field

176 - Data Too Long

177 - Validate Record Failed

178 - Not in List

180 - Task Based Billing Switch Conflict

186 - Balance Mismatch

240 - File Encrypted

241 - File Not Encrypted

500 - PracticeMaster and Tabs3 / TAS Files Are Not Synchronized

501 - PracticeMaster and Tabs3 / TAS Files Are in Pending Sync Mode

600-775 - Ledger Validation Errors (Note: If you encounter a ledger validation error, please contact Tabs3 Support for assistance.)

Note: If you attempt to manually correct the errors found by the Data File Integrity Check, run the Data File Integrity Check again after your corrections. If you restore from a backup due to corrupted data files, run the Data File Integrity Check program after you have restored to verify that the restored data is not also corrupt.

Note: The last five Data File Integrity Check Error Reports containing error messages are saved in the current working directory as PDF files. These files can be accessed from the Support Log. The last Error Report can also be accessed from the Data File Integrity Check window. Additionally, DFIC information is saved to a log file named T3DFIC.LOG and can be opened with a text editor if necessary. This log file is deleted and recreated the next time the Tabs3 Billing Data File Integrity Check program is run. For additional information about the Data File Integrity Check Error Report, see Knowledge Base Article R11796, “Data File Integrity Check Error Reports.”

See also:   Verification File Errors
  Knowledge Base Article R11819 - Data File Integrity Check Errors
  Knowledge Base Article R11796 - Data File Integrity Check Error Reports