We were able to fix the file using that knowledge base article. We read that visual fox pro 7 doesn't care if the number of records in the header file match the total number of records. So out of curiosity I made a copy of the corrupt table. Added to a dbc in visual, converted it to a Visual fox pro table. Then I used a "copy to" command to copy the file back into a foxpro 2.6 file and that worked too.

>I just found article Q98743 which could help. (found it with google but coudln't find the article with the ms search on the knowledge base, go figure) any other suggestions?
>
>>Hi,
>>
>>Our server crashed today. Once it was back up and running we got the dreaded "not a database" error when trying to open a dbf. It is a foxpro 2.6 table. What are some steps I could make to try to recover this file? We have the file backed up but I would prefer to try all alternatives first as it had been modified since the last backup last night.
>>
>>Thanks,
>>Chris