Glad to hear that my suggestions were helpful. I had to use my own procedure after I made that post and realized that I should make one change:

1) Copy the corrupted table and its DBC to a SAVE directory.
2) Copy the good empty table with its FPT file but NOT its CDX file to the working directory.
3) USE the good table and verify that it has no records.
4) APPEND from the the corrupted table.


VFP made me delete the CDX file before I could finish the APPEND so this change saves a step.

There are lots of good words for Doug Hennig's Stonefield Tools on this forum. I have purchased them but not integrated them with my app yet.

I rushed them into use to try to fix a corrupted file in a production environment but that just made things worse. When I installed the Tools they wanted to modify my DBC. I let it go ahead which was a mistake because it added references to Stonefield classes in my DBC. Then my app would not run at all. (Doug you might want to include a more obvious warning about this.)

I can see now that I need to integrate the tools in the development environment first.

Peter Robinson



>Thanks Peter, this worked - as I'm sure would the other suggestions. In fact I found that if an empty CDX file is copied over the corrupted one, the DBF can be 'USED' and then I can reconstruct it or issue REINDEX. But it does mean keeping those empty files!
>
>David