>>>>Has the DBF file exceeded 2GB size? This could make repairs a wee bit trickier.
>>>
>>>This was a FP 2.6 and below issue. VFP doesn't let table exceed 2GB.
>>I've seen situations in VFP applications where a table "crashed" because it went over the 2GB size limit -- the INSERT or APPEND command would indeed add a record and the record count would update -- but soon afterwards you'd get a runtime error. Indeed, as you say, VFP won't allow the table to exceed 2GB -- you get an error that point (unfortunately you still have a table that now cannot be opened). Fixing it requires that you either decrement the record count (and lose the last record added), or use an external program to effect the repair. The low-level file functions in VFP will work for the first type of solution, but not for recovery of any data past the 2GB size, as the low-level file functions in VFP appear to be subject to the same 2GB limitation.
>
>You can't open files with VFP low-level file functions. I used Parserat for .DBF files exceeded 2GB.

Perhaps that should be qualified -- the low-level functions in VFP *can* be used if the files in question have not exceeded the 2GB size. If the files reach or exceed 2GB, then the low-level functions in VFP *won't* work because they are subject to the 2GB size limitation. One thing I have not checked yet is to see if using direct calls to the Win32 API would allow us to circumvent the 2GB limitation or not (I would assume this should be possible, as I recall seeing a few 32-bit programs that can handle files larger than 2GB in size -- provided you weren't dealing with filesystem like FAT16 that had an inherent limit of 2GB or less).