Dealing with the "Memo file missing/invalid" error

The usual cause of the "Memo file missing/invalid" error message for FoxPro users is that the next free block pointer at the beginning of the memo file has been corrupted although more extensive damage is also possible. Corruption of this pointer often results from an abortive shutdown while the file is open. It is a problem that is easily repaired by dSALVAGE with a single keystroke. Some versions of FoxPro will also allow you to correct this problem.

An addition, the memo file bytes that hold the memo block size information can be corrupted, but this form of damage is rather rare. The hex/ASCII editor in dSALVAGE can be used to correct this information.

Return to the dSalvage main page