It is well known, that if a FoxPro program (any version) appends/writes to a table and computer crashes, the table becomes bad. Next time when FoxPro uses it, an error appears, like this:

Not a database file (Error number 15)
Table "name" has become corrupted. The table will need to be repaired before using again. (Error number 2091)
MEMO file is missing/invalid (Error number 41)

For several years of working with large data massifs and many clients, we discovered that in 99 % it is possible to recover tables and memo files with small or no loss of information.

One of the problems occurs when FoxPro appends records. FoxPro engine writes buffers o?n disk in this order: first changes record number in the header of the table, and after changes the size of the file and writes data. Better way is to reverse order of this two operations, but it is embedded in the Foxpro engine.

We are using this utility with