PowerChurch Plus relies heavily on its data files. During normal daily use, it is not uncommon for some data files to be accessed hundreds if not thousands of times. If your computer gets abruptly turned off or experiences a power surge while PowerChurch Plus is accessing one of these files, it is possible to corrupt that file's header record. When this occurs, you will begin receiving the error message "Not A Table/DBF file" when trying to access certain areas of PowerChurch Plus.

Normally, a data file's header record can be easily repaired using a small utility included in PowerChurch Plus. This document will explain the process for repairing a corrupted header record using this utility.

1. In PowerChurch Plus, go to the Setup menu.

2. Click on the Database Manager option.

3. You should then see a gray screen with a dot prompt in the lower left corner. From this dot prompt, enter the next few commands.

4. It is important to determine which data file may be corrupted. To do this, use the table below.

5. Type: use filename (substituting filename with a file from the list to the right) and press enter. For example, if you were experiencing a problem when entering the membership module, you might enter: use ma.dbf.

6. If you receive another dot prompt without an error message, then the file you chose is not corrupted. You should then repeat step five, substituting the next file in the list. If none of these files seem to be corrupted, then contact technical support for further assistance.

However, if you receive an error message such as "Not a Table/DBF," then the file you selected is indeed corrupted. Continue with step seven.

7. When you have found a corrupted file, type: do recntwin with "filename" (again, substituting filename with the damaged file's name) and press enter. For example, if there was a problem with the ma.dbf file, you would fix it by entering: do recntwin with "ma.dbf".

8. After you have found and fixed any files that were corrupted, simply press the ESC key to leave the Database Manager. At this point, it is very important to Reindex your data files. If the "Not a Table/DBF" error message persists, you should contact Technical Support for additional assistance.

Accounting
apauto.dbf
apopen.dbf
appaid.dbf
apvend.dbf
arcust.dbf
aritems.dbf
aropen.dbf
arpaid.dbf
faaccts.dbf
factrl.dbf
famstr.dbf
faprior.dbf
fatrans.dbf
prdesc.dbf
prempl.dbf
pritems.dbf
prpaid.dbf
prtables.dbf

Contributions
co.dbf
cofund.dbf
copled.dbf
cotrans.dbf

Record Keeping
ed.dbf
eq.dbf
mu.dbf
se.dbf