>>>>The maximum size of a VFP table is 2 GB (a limitation that beats up Access' database limitation of 1 GB total MDB size). When a table is opened, the database manager in my framework compares the table against this limit and also determines if there is enough diskspace available to add an additional 100 records to the table. This allows the user to be alerted well in advance (hopefully) of any potential space issues.
>>>>
>>>>Question: does anyone know if the size limitation also applies to CDXs?
>>>
>>>Search on VFP help for "system capacity", there is mention of the indexes.
>>
>>The only limitation I could see was on the bytes per key. Does this indicate that the size of the actual CDX is not an issue?
>
>No single file can exceed 2GB.

I don't agree with the above statement...

As much as I know, Visual FoxPro does not impose a limit on the size of a .CDX file. On the other hand, the operating system in use and its file system may impose such a limit.

If you're trying to say that all files, wheter related or unrelated to VFP, are limited to 2GB than I don't agree with that either.

The FAT file system has a 2GB limit on partitions...therefore in this instance, a file may not exceed 2GB. However, FAT partitions under Windows NT may be up to 4GB in size.

The NTFS file system of Windows NT has a file size limit of 2^64 bytes (16 exabytes...18,446,744,073,709,551,616 bytes!!!) However, underlying hardware limitations may impose additional partition size limitations in any file system. Particularly, a boot partition can be only 7.8 GB in size, and there is a 2-terabyte limitation in the partition table.

Enough said...let me know if you do find a statement that indicates any limitations on .CDX file sizes.