I may be wrong on this, but I recall, reading that windows itself has a 2 gig file size limit, so the problem is not so much fox, but a litmit of the os.

Bob Lee

>Only the fpt was 2GB, the dbf was much much smaller. I thought the limitation only applied to DBFs not corresponding fpt files...
>
>I am incorrect about this?
>
>>>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.
>>
>>The table was not corrupted, it hit the 2GB file size limit in VFP, and the VFP memory pointers became unable to access it. Even if the table hadn't been 'repaired', you'd still be screwed.
>>
>>If you do find a usable, recent copy of this table, you need to _immediately_ restrict access to it while you restructure your data, moving it to smaller files. Whether this means splitting the table in half record wise or column wise depends on the structure of the table and your preference. It might also be time to start thinking about a database that's designed to handle data of that volume.