>700K not 700M, so I think I do indeed have a problem...good question though...
>
>>>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...
>>
>>Stupid question time. . .
>>
>>Are you **sure** it's corrupted. A .FPT going from 2gig to 700meg needn't be an unusual thing.
>>
>>good luck,
>>
>>JimN
And I had my glasses on too!!!
So I presume that users have found that there is missing information?... I agree that going from 2 gig to 700K is wild, but if you've got a memo file that changes a lot but only tiny bits per change *AND* the table is not PACKed for a long time (very very long, like maybe 4 years), it seems it could still be OK.
Good luck (again)
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only