>>>Hi,
>>>
>>>My VFP5a written application is using Foxpro 2.50 free table to run
>>>with my clipper 5.2 written application.
>>>
>>>However, we happened to encountered problems of the free table when
>>>reaching file size of 2G will be corrupted.
>>>
>>>I can't find any informations on the file size limit of Foxpro 2.5
>>>or their maximum records in VFP5a.
>>>
>>>Anyone know of the file size limit and their capability. Please
>>>let me know in details and possiblities of any rememdy for this problem.
>>>
>>>Thank a lot
>>
>>From the FPW 2.6 help file:
>>
>>"Max. # of records per table 1 billion*
>>Max. # of chars per record 65,000
>>Max. # of fields per record 255
>>Max. # of open DBFs 225
>>Max. # of chars per field 254
>>Max. # of chars per index key (IDX) 100
>>Max. # of chars per index key (CDX) 240
>>Max. # of open index files per table unlimited**
>>Max. # of open index files in all work areas unlimited**
>>Max. # of relations unlimited
>>Max. length of relational expressions unlimited
>>* The actual file size (in bytes) cannot exceed 2 gigabytes for single-user or exclusively opened multi-user tables. Shared tables with no indexes or .IDX indexes cannot exceed 1 gigabyte. Shared tables with structural .CDX indexes cannot exceed 2 gigabytes.
>>** Limited by memory and available MS-DOS file handles. Each .CDX file uses only 1 file handle. The number of MS-DOS file handles is determined by the CONFIG.SYS FILES parameter."
>
>Hi George,
>
>Thank for the information.
>So, I am safety conclude that those free table having size greater
>than 2G will had problem like in my case.
>
>Could it be the size limitation also cause problem of
>data corruption either at the end or middle of the free table
>like I encountered before ?
>
>In my case, it reported of 'not a database file' when
>I use a third party program to view it.

I really don't know about corruption. I've never seen the effects of having a table exceed the 2gb limitation. It might, however, cause the report of the table not being a database file.