Table Check Utility
The new update program is stricter about problems with data files than our old update process. While this may lead to the update failing in certain cases where data files may be corrupt or invalid, finding and fixing these problematic files will help maintain system stability going forward.
To help identify these problems, we have a new table check utility named tablecheck.exe that can be downloaded from the Downloads page on our website or obtained via patches if you are currently on version 2024.2 or later. You can simply drop the file in to your EvoERP or DBAMFG root directory. Run this utility by double clicking on it in File Explorer to do some basic checks on your data files. This utility does not modify data files but offers various checks to catch common problems. In our testing, typically doing just the quick file version check described below then rebuilding any old files catches the vast majority of problems that occur during the new update process because these problems tend to appear on old, mostly unused files that have not been updated or rebuilt in a long time but remain in the system for backwards compatibility or are used by DBA Classic. It does check the data for all companies and you need to address anything it finds in any company because the update will be updating all of them.
File Version Check
This option is a quick check to determine the Zen/Pervasive version of each data file and number of records. Any files older than version 9.5, especially below version 6.0 or listed as unknown version, should be rebuilt using the Pervasive/Zen rebuild tool to at least version 9.5. Files between 7.0 and 9.5 are not critical to rebuild now and the utility will only display them as a problem if they are above a certain size as these versions are not properly supported if the files become too large. Any file that is a version prior to 9.5 can segment or become corrupted if it exceeds 2 GB in size so any file of an older version approaching the 2 GB limit should be rebuilt.
The version check scan will return a list of files along with the version and number of records for any problematic files. If the file has no records, you can reinitialize it in Evo-ERP at TAS-E which will replace the file with a new empty one. For assistance rebuilding or initializing the files, please contact tech support.
This file version check typically only takes a minute or two to run and can safely be run while the system is in use. Once files to be rebuilt are identified by this program, the rebuild needs to be run with nobody in the system.
Record Scanning
There are several options for scanning records in files. You can scan by the physical order, first index, or all indexes. For large tables, this process can take a while especially if you choose to scan all indexes. Some files may not have any numbered indexes. The option to scan all indexes also scans by physical record order.
The utility will first check the number of records reported to be in the file, then scan in the order requested counting every record. At the end, it will validate the number of records scanned matches the expected number of records. We do not recommend running the record scan while users are in the system because the number of records in a file could change while scanning if a user performs an action to either remove or add records.
This record scan can be a simple way to validate that the system can at least reach all the records in the file without error and that the number of reachable records matches the expected number of records in the file but it is not a comprehensive file validation tool as it does not compare the actual record contents with the dictionary.
