>>>>>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.
>>
>>It's worse than that. VFP will keep inserting records until the file is well past 2GB. And then at some point it won't open it or whatever.
>>
>>I had the opportunity to attempt to fix a 2GB+ VFP table and it was a tough go. I found a program written in C that would pull the data and put it into text files or something and then I had to try to piece it back together.
>>
>>Yes, the low level file functions in VFP are limited to 2GB and less.
>
>As the low-level file functions in VFP are limited to 2GB, has anyone checked to see if going directly to the Windows API would be a workaround?

used the FSO for accessing beyond 2GB, but never tried to fix dbfs with it