Hi Russell.

>(1) Invalid DCT (DBC index) file

The DCT is actually the memo for the DCT; the DCX is the DBC index. Fixing an invalid DCX file is easy: just delete it. VFP will recreate it the next time the DBC is opened. Fixing a DCT is like fixong a corrupted memo (see below).

>(2) Invalid index file for DBF

As Will mention, SDT will handle that.

>(3) Corrupt Memo File

SDT can handle table and memo header corruption. If the damage extends into the data area, FoxFix from Xitech or Recover from Abri are the tools to use.

>(4) Tablename not found in DBC, but exists on disk (has been dropped)

That may not be a problem if that was the intention. If you want the table back in the DBC, add it (you'll have to recreate any long field names, triggers, default values, etc.). If you don't want the table added back to the DBC but are getting an error when you open the table because it still contains a backlink to the DBC, use FREE TABLE to eliminate the backlink.

>(5) Tablename in DBC, but not in current DBC path

VALIDATE DATABASE RECOVER can resolve this for you, but only in a VFP Command window. If you need to resolve this programmatically, SDT has a method that can fix incorrect paths, both from the DBC to the table and from the table to the DBC.

Doug