>While I'm a big fan of SDT, and think that using SDT is a great idea, it's too late to help the problem if you weren't already using SDT when the problem occurred, and SDT's repair mechanisms for memo fields are not comprehensive; while it will recover to the point of letting you continue working with the database, I've found that I often lose or mislink memo content after recovery when some kinds of memo errors occur. A better choice for me has been dSalvage Professional, which can be purchased through Hallogram if nowehere else.

The HALLoGRAM website (http://www.hallogram.com/dsalvge/index.html) states that "The current version of dSALVAGE is not compatible with Visual FoxPro files." Do you know something we don't? (and I wouldn't be surprised if you did <g>)

As for SDT, I don't know why you would need to have been using it before the problem occurred. Theoretically, you could create the SDT meta data after the fact and still run REPAIR(). I admit I haven't tried this, though.