The information in this article applies to:
This article provides examples of the Data File Integrity Check Error Reports in each Tabs3 or PracticeMaster system, along with explanations of the information contained in each report.
Each time a Data File Integrity Check (DFIC) program is run in a Tabs3 or PracticeMaster system, a log file is created in the program directory. This file consists of information identical to the Data File Integrity Check Error Report (if any). The file name of this log file corresponds to the system in which the DFIC is run. The existing log file is deleted to allow for creation of a new log file with the same file name. DFIC log files can be accessed using any text editor (e.g., Windows Notepad, WordPad, etc.). The file name for each system's DFIC log file is provided below.
|
System |
Log File |
|---|---|
CMDFIC.LOG |
|
T3DFIC.LOG |
|
T3AFIC.LOG |
|
A3DFIC.LOG |
|
G5DFIC.LOG |
|
T4DFIC.LOG |
|
R3DFIC.LOG |
The following is an example of the PracticeMaster Data File Integrity Check Error Report. Clicking a column heading on the report will display the definition for that column.
Date: 11/15/2011 PracticeMaster Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Code AOP Name AOP Title File Name File Title Field ID <Index> Rec # Client ID (Key)
54 CMSYSTEM System Files CMJRNL Journal Client_ID 5 110.01 - N
____________________________________________
DFIC was started at: 09:48 AM on 10/15/2011
DFIC ended at: 09:48 AM on 11/15/2011
1 error(s) were found
|
The following table explains the contents of each column on the PracticeMaster Data File Integrity Check Error Report.
Column Name |
Description |
|||||||||||||||
The Error Code indicates what type of error has been found. The following KB Articles list each possible error code and its meaning:
In the example shown above, the Error Code is 54. |
||||||||||||||||
The AOP Name column shows the directory name of the Area of Practice associated with the file that has the error. |
||||||||||||||||
The AOP Title column indicates the title of the Area of Practice associated with the file that has the error. |
||||||||||||||||
The File Name column shows the file name of the data file in which the error has been found. |
||||||||||||||||
The File Title column provides the description of the data file in which the error has been found. |
||||||||||||||||
Field ID <Index> |
The Field ID <Index> column indicates the field or index containing the error. |
|||||||||||||||
The Rec # column indicates the position of the record in the data file. This information can be used to access the record via the Load Record program, which allows editing of a specific record when the record number is the only information available. The Load Record program can be accessed by selecting Edit | Load Record from the List tab of any PracticeMaster data file. |
||||||||||||||||
Client ID (Key) |
The Client ID (Key) column shows the Client ID or key field associated with the record that has the error.
|
The following is an example of the Tabs3 Data File Integrity Check Error Report:
Date: 11/15/2011 Tabs3 Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Client ID Key<Ref#> Seq No
1 11 Invalid Category TK By Cat Prod Category Number 4 :8 278
Key for the 'Key<Ref#>' field.
Non-listed files and errors 55, 72, 73, and 74 cause this field to be blank.
Error 69 reports the index number in this field.
File Key represents
Billing Freq Frequency ID
Budget Phase Task ID
Category Category Number
Cat Prod Category Number
Client Fund Reference Number
Fee Rate Timekeeper Number
Cost Rate Tcode/Task Code
Ledger Reference Number
Ledger Detail Reference Number
Location Location ID
Pymt Alloc Ledger Reference Number
Rect Alloc Record Type
Stmt Code Code ID
Stmt Note Note ID
Task Code ID
Timekeeper Timekeeper Number
TK by Cat Prod Timekeeper Number Category Number
TK by Tcode Prod Timekeeper Number:Transaction Code Number
TK Prod Timekeeper Number
Fee Reference Number
Cost Reference Number
Pymt Reference Number
Tcode Transaction Code Number
Fee Verif User ID
Cost Verif User ID
Pymt Verif User ID
Flat Fee Verif User ID
Fund Verif User ID
Split Fee Verif User ID
Transf Verif User ID
Upd Stmt Verif User ID
Wrt Off Verif User ID
Wrt UpDn Verif User ID
____________________________________________
DFIC was started at: 09:52 AM on 11/15/2011
DFIC ended at: 09:52 AM on 11/15/2011
Totals:
Error
Count Code Error Description
1 11 Invalid Category
1 error(s) were found
Tabs3 release date: 10/24/11
|
The report includes a key that explains the contents of the Key<Ref#> column. The following table explains the contents of each column on the Tabs3 Data File Integrity Check Error Report.
Column Name |
Description |
The Data File Integrity Check keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. |
|
The Error Code indicates what type of error has been found. The following KB Articles list each possible error code and its meaning:
In the example shown above, the Error Code is 11. |
|
The Error Description column provides a description of the error that has been found. |
|
The File Name indicates the file in which the error has been found. |
|
The Field column indicates which field in the affected file contains the error. |
|
The Client ID column indicates which client the affected record belongs to, if any. |
|
The meaning of the information in the Key<Ref#> column varies depending on the file in which the error was found. |
|
The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given
file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for the use of our Technical Support Representatives only. |
The following is an example of the Tabs3 Archive File Integrity Check Error Report:
Date: 11/15/2011 Tabs3 Archive File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Client ID F/C/P Type Seq No
1 51 Invalid ID Arch File Client Id 123.sss F 11
____________________________________________
AFIC was started at: 04:47 PM on 11/15/2011
AFIC ended at: 04:47 PM on 11/15/2011
1 error(s) were found
|
The following table explains the contents of each column on the Tabs3 Archive File Integrity Check Error Report.
Column Name |
Description |
The Archive Data Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. |
|
The Error Code column indicates what type of error was found.
KB Article R10771, "Archive File Integrity
Check Errors," lists each possible error code and its meaning. |
|
The Error Description column provides a description of the error that was found. |
|
The File Name column indicates the file in which the error was found. |
|
The Field column indicates which field in the Archive file contains the error. |
|
The Client ID column indicates the client to which the affected record belongs. |
|
The F/C/P Type column indicates whether the archive transaction that contains the error is a (F)ee, (C)ost or (P)ayment transaction. |
|
The Seq No column indicates the sequence
number (i.e., the unique key value that identifies each record in a
given file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for the use of our Technical Support Representatives only. |
The following is an example of the APS Data File Integrity Check Error Report:
Date: 11/15/2011 APS Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Vendor Key<Ref#> Seq No
1 5 Missing Federal ID Vendor Federal ID 120.00 <120.00> 4
'Key<Ref#>' Legend.
Non-listed files and errors 55, 72, 73, and 74 cause this field to be blank.
Error 69 reports the index number in this field.
File Key Represents
---- --------------
Vendor Vendor
Invoice Reference Number
Bank Bank Account
Recurring Entry Record Number
Verification User ID
__________________________________________________
DFIC was started at: 03:35 PM on 11/15/2011
DFIC ended at: 03:35 PM on 11/15/2011
1 error(s) were found
|
The following table explains the contents of each column on the APS Data File Integrity Check Error Report.
Column Name |
Description |
The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. |
|
The Error Code indicates what type of error has been found. The following KB Articles list each possible error code and its meaning:
In the example shown above, the Error Code is 5. |
|
The Error Description column provides a description of the error that was found. |
|
The File Name column indicates the file name of the file containing the error. |
|
The Field column indicates which field in the affected file contains the error. |
|
The Vendor column indicates the vendor number associated with the record containing the error. |
|
The meaning of the information in the Key<Ref#> column varies depending on the file in which the error was found. |
|
The Seq No column indicates the sequence
number (i.e., the unique key value that identifies each record in a
given file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for the use of our Technical Support Representatives only. |
The following is an example of the GLS Data File Integrity Check Error Report:
Date: 11/15/2011 GLS Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Acct # Key<Ref#> Seq No
1 10 Invalid character Journal Desc 110.05 <247 > 247
'Key<Ref#>' Legend.
Non-listed files and errors 55, 72, 73, and 74 cause this field to be blank.
Error 69 reports the index number in this field.
File Key represents
---- --------------
Journal Entry Record Number
Department Department Number
Journal Name Journal Number
Recurring Entry Record Number
Client Client Number
Verification User ID
--------------------------------------------------
DFIC was started at: 04:49 PM on 11/15/2011
DFIC ended at: 04:49 PM on 11/15/2011
1 error(s) were found
|
The following table explains the contents of each column on the GLS Data File Integrity Check Error Report.
Column Name |
Description |
The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. |
|
The Error Code indicates what type of error has been found. The following KB Articles list each possible error code and its meaning:
In the example shown above, the Error Code is 10. |
|
The Error Description column provides a description of the error that was found. |
|
The File Name column indicates the file name of the file containing the error. |
|
The Field column indicates which field in the affected file contains the error. |
|
The Acct # column indicates the account number associated with the record containing the error. |
|
The meaning of the information in the Key<Ref#> column varies depending on the file in which the error was found. |
|
The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given file) for the record that contains the error.
Note: The sequence number is not visible in any data entry window, and is provided for the use of our Technical Support Representatives only. |
Note: The G5DFIC.LOG file is always created in the GLS program directory, regardless of which GLS client is selected when the DFIC is run. For example, if you select GLS client 1 and run a Data File Integrity Check, then select GLS client 2 and run the DFIC program again, the G5DFIC.LOG file will contain the results of the second DFIC only, regardless of each client's GLS data path.
The following is an example of the TAS Data File Integrity Check Error Report:
Date: 11/15/2011 TAS Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code Error Description File Name Field Trust ID Key<Ref#> Seq No
1 6 Mismatched Fed ID Master Federal ID 200.03 <3 6
'Key<Ref#>' Legend.
Non-listed files and errors 55, 72, 73, and 74 cause this field to be blank.
Error 69 reports the index number in this field.
File Key represents
Master Trust Account and Bank Account
Transaction Reference Number
Bank Bank Account
Payee Payee Name
Attorney Attorney Number
Verification User ID
____________________________________________
DFIC was started at: 09:11 AM on 11/15/2011
DFIC ended at: 09:11 AM on 11/15/2011
1 error(s) were found
|
The report includes a legend that explains the contents of the Key<Ref#> column. The following table explains the contents of each column on the TAS Data File Integrity Check Error Report.
Column Name |
Description |
The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. |
|
The Error Code indicates what type of error has been found. The following KB Articles list each possible error code and its meaning:
In the example shown above, the Error Code is 6. |
|
The Error Description column provides a description of the error that has been found. |
|
The File Name column indicates the file name of the file containing the error. |
|
The Field column indicates which field in the affected file contains the error. |
|
The Trust ID column indicates the Trust ID associated with the record containing the error. |
|
The meaning of the information in the Key<Ref#> column varies depending on the file in which the error is found. |
|
The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given
file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for the use of our Technical Support Representatives only. |
The following is an example of the Tabs3 Remote Data File Integrity Check Error Report:
Date: 11/15/2011 Tabs3 Remote Data File Integrity Check Error Report Page: 1
Burns, Jensen & Powers, P.C.
Error
Count Code File Name Location Description Seq No
1 10 Fee Client 560.00 Ref 4 Fee Hold/Print 9
____________________________________________
DFIC was started at: 12:24 PM on 11/15/2011
DFIC ended at: 12:24 PM on 11/15/2011
1 error(s) were found
|
The following table explains the contents of each column on the Tabs3 Remote Data File Integrity Check Error Report.
Column Name |
Description |
The Data File Integrity Check program keeps track of how many errors it has found, cumulatively. The Count column indicates when each error occurred in the sequence. |
|
The Error Code indicates what type of error has been found. The following KB Articles list each possible error code and its meaning:
In the example shown above, the Error Code is 10. |
|
The File Name column provides a description of the file containing the error. |
|
The Location column indicates the client or record with which the error is associated. |
|
The Description column describes the field that contains the error. |
|
The Seq No column indicates the sequence number (i.e., the unique key value that identifies each record in a given
file) for the record that contains the error. Note: The sequence number is not visible in any data entry window, and is provided for the use of our Technical Support Representatives only. |
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