The information in this article applies to:
A Data File Integrity Check (DFIC) Error 10 indicates a non-keyboardable character has been encountered.
Normally, all you need to do is to edit the record shown on the Error Report using the appropriate data entry program and change the invalid character to the correct character. If several reference numbers have this type of error, it usually indicates that several records have been corrupted and you should probably restore your data files from a backup copy.
Note: In PracticeMaster, if you preview the Error Report, you can easily drill down to the record with the error by moving the mouse over the error and clicking it when it is highlighted in yellow.
Sometimes it is unclear how to correct a DFIC error 10. For example, the DFIC error report may state that there is an error in the address field for a client, but when you view the record, it looks fine. Also, a DFIC error 10 can occur in a field that is not visible on any data entry screen.
The DFIC program scans each data field looking for values that are outside the range of valid ASCII characters. If the program is configured to allow Extended Characters, then invalid character checking is performed for the fields that allow Extended Characters. When using Version 12.1 and earlier, in order for a Tabs3 or PracticeMaster program to allow extended characters, the following parameter must be added to the STI.INI file. Under the [STI Options] heading, add "Allow Ext Chars=Yes" (excluding the quotation marks). (Note: With the release of Version 12.2, all Tabs3 and PracticeMaster software is automatically configured to allow extended characters. Therefore, the "Allow Ext Chars=Yes" parameter no longer needs to be added to the STI.INI file when using Version 12.2 or later.)
Each character field has a maximum length. For example, the address line fields in the Client file are 36 bytes. This allows for 35 characters of address information with a terminator character (the NULL char) in byte 36. If the address is 12 characters long, the terminator is placed in byte 13. The characters following the terminator should be either NULL (0) or a valid character. When the field is displayed on the screen, anything after the terminator is not shown. DFIC checks the bytes before and after the terminator. If there happens to be an invalid character after the terminator, it will report it as an error 10. Of course, when you try to correct the invalid character, you cannot see the invalid character because it is after the terminator.
It is possible to get an error 10 in the Hold/Pay field of an APS invoice record that has been paid by a check due to data corruption. The Hold/Pay field should have "Pay" in it when an invoice has been paid. The error 10 indicates that this field is corrupted and it will appear as blank on the screen. As a result, the invoice cannot be posted using the Post Checks program. This can cause incorrect amounts to post for a check that pays multiple invoices including the affected record. The affected invoice cannot be deleted since it has been paid.
Use the following steps to remove an invoice that has an error 10 in the Hold/Pay field:
Note: Invoices with a corrupted Hold/Pay field cannot be posted by the Post Checks program. Therefore, vendor analysis totals are not affected by deleting and re-entering the invoice. However, if there were other invoices paid by the same check, and the check was posted, you will need to run Post Checks again after recreating the affected invoice as a manual check.
Note: If the affected invoice was part of an extended description invoice, we recommend that you void the check and reprint it after deleting and recreating the affected invoice as described in the procedure above. Also, if the check was posted, run a GLS Journal Report to confirm that the correct reversing entries were created by voiding the check.
You can correct the invalid character(s) by filling out the entire field to the last possible position (e.g., all 35 characters for an address field) and saving the record. Next, edit the field again by changing the data back to the correct information and re-save the record. If you do not save the record with the field "maxed out", any invalid character(s) beyond the terminator will not be overwritten.
Note: This error should not have occurred in the first place. Experiencing error 10s may indicate there are problems with the computer system. In a network environment, make sure that the file server is updated to the LATEST patch level, all client redirectors have been updated and the appropriate registry changes (i.e., opportunistic locking) have been made. Refer to R10200 in our Knowledge Base for additional information.
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