<< Click to Display Table of Contents >>

Check File Integrity (DBA Classic)

Purpose of Program

Use this program to check your data files for possible corruption.  If you are in an entry program and data does not respond in a normal fashion (such as when entering a item number you get the wrong description or data appears to be missing), this can signal problems with a particular file.

If a data file is found to be corrupt, sometimes it can be corrected via UT-C  Re-Index File.  Re-indexing may be helpful in recovering a file if the file key structure is corrupted, which can be caused by a power failure or damage to the hard drive.

General Program Operation

The program will check the files in the current company only.  To check the files of another company, change to that company, then run the program.

GET EVERYONE OFF THE SYSTEM: Get all users off the system before running this program.  In order to check the files you must have 100% access to all records in each file, so no one can be using any programs while you do so.

If you plan on checking all your files, the Enter Path and File Name+Ext Here default value is normally left as is (the program automatically senses the correct path and file extension for the company you are in).  You can however, limit the files that will be checked through the use of wildcards.  For example, if you just want to check Accounts Payable files, you can enter BKAP*.B (if in the default or "blank" company), or TESTDATA\BKAP*.B99 (if in company 99).  See File Names for a list of file names used within each module.

Next, click on the Find Files button.  You will then see the program identify and check the files.  When finished, the files will be displayed in the bottom window, with a column for the File Name, its Status (file format), and the Num Recs (number of records in the file).

Any files that fail the test will be listed in the Exceptions windows in the lower right portion of the screen.  If the program had trouble reading a file, which could happen due to corruption of the file header or if a file with a B* extension was not a true Btrieve file, the file will be marked with an N in the Type column.

If the file has an L in the Type column, the file was locked by another user (which shouldn't happen if all users are out of the system).  Verify that all users are out of the system and check that file(s) again.

If a true Btrieve file is on this list, you can try to re-index the program through UT-C  Re-Index File(which reads the file from the data dictionary rather than directly).  If that does not work, you will have to recover the file from the last good backup.

Password Security

The use of Check File Integrity generally confined to system administrators and is not something that would be run by the average user.  Access to this program can be controlled via PS-A  System Users/Passwords.  If you want to deny access to this program, set the Use Maintain Database and Check File Integrity? field on the user logon screen in PS-A to N.