DFIC Error 72 - File Structure is Corrupt (Bad DODA)

Last reviewed: 01/11/2010
Article ID: R10617

The information in this article applies to:

• Tabs3 Billing Software Version 15, 14 & 12
• Tabs3 Remote Entry Software Version 15, 14 & 12
• Tabs3 Trust Accounting Software (TAS) Version 15, 14 & 12
• Tabs3 General Ledger Software (GLS) Version 15, 14 & 12
• Tabs3 Accounts Payable Software (APS) Version 15, 14 & 12

SUMMARY

This error indicates that the structure of the data file shown on the Error Report does not match the structure required by the software.

This error can occur for one of four reasons:

• Validation files were created using a new version of Tabs3, and were used with a prior version of Tabs3 Remote Entry Software.
• A new version of Tabs3 Remote Entry Software was installed, but data files from a prior version remain.
• Restored data files from the older version.
• Data corruption.

Tabs3 Remote Entry Software Note: When Tabs3 Remote Entry Software is updated, remote data files are not converted to the new version. Therefore, before updating any Tabs3 and PracticeMaster software, Tabs3 Remote Entry data must be merged into Tabs3. See the Tabs3 Remote Entry Software Instructions below for more information.

RESOLUTION

To correct this error:

1. Determine the cause of the error (listed above) and then perform one of the following:
• Install the correct version of the software that matches the data files, confirm that no DFIC errors exist, and then attempt the update process again.
  Remote Note: Merge Tabs3 Remote data into Tabs3 before attempting the update process.
• Restore the data files from a backup made prior to receiving the first DFIC error 72.
2. Run the Data File Integrity Check.

Note: The Description shown on the Error Report will include the label "Bad DODA", which is for Technical Support purposes only.

Tabs3 Remote Entry Software Instructions:

This error is caused by the presence of data files for a different version than the software in the Tabs3 Remote current working directory.

When preparing to update Tabs3 and PracticeMaster software, always merge Tabs3 Remote data first. The Remote data must be merged before updating because Remote data files are not converted when the software is updated. The Remote and Billing software versions must match in order for data to be merged from Tabs3 Remote to Tabs3 Billing Software. Confirm that the versions match using the Help | About window.

After merging Remote data, all RMT*.* and R3*.* files must be deleted from the Tabs3 Remote current working directory, excluding R3CUSTOM.DAT, R3TASK.DAT, and R3TERM.DAT.

To correct this error:

1. Install the correct version of the Tabs3 Remote that matches the Remote data files.
2. In Tabs3 Remote, print a Transaction File List for all transactions (Reports | Transaction File List).
3. Delete all RMT*.* and R3*.* files from the Tabs3 Remote current working directory.
   Note: Do not delete R3CUSTOM.DAT, R3TASK.DAT, or R3TERM.DAT.
4. Install the version of Tabs3 Remote that matches the current Tabs3 Billing Software installation.
5. Create new Remote Validation Files in Tabs3 (Maintenance | Integration | Create Validation Files).
6. Copy the new Remote Validation Files into the Tabs3 Remote current working directory.
7. Run the Data File Integrity Check in Tabs3 Remote.
8. Reenter the transactions that were printed on the Transaction File List.

REFERENCES

• KB Article R10167 - Data File Integrity Check Errors in Verification Files

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-2010 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