>I have a HUGE problem. Client has an application in VFP6 SP3. The had a table (notice the past tense), events.dbf, that had a 2GB memo file. Appears that the file was corrupted. Someone at client was using VFP interactive, when the file was opened VFP prompted Delete or Repair, the user answered repair. All of a sudden the fpt file is 700K instead of 2GB.
>
>Client's last backup is from February.
>
>I've never seen anything like this happen before & I've been around Fox a long time, maybe I've just been lucky. Do I have a prayer to correct this problem, and if so how?
>
>Thanks in advance for everyone's help...

A backup that is 4 months old? It's deja vu all over again!!!!! Nooo. Nooo. Mumble, mumble, groan, groan. It's only a dream, it's only a dream. Wake yourself up. < Snap > Whew!!! Thank goodnes that was only a bad dream, and it's not my customer. What a relief. < bg >

I would say they are SOL unless they can live with the February data. You could move the original DBF/FPT to a backup folder and do a restore of just those 2 files to the original location. Then you can compare the 2 tables and try to add the new stuff from the original table into the restored table.

Is there any process where the original files may have been sorted or copied to a temp file name, closed, erased then had the temp files renamed back to the original file names? If so, you mith try an unerase utility or, if on a Novell drive, Salvage.