>>>>>>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.
>>
>
>I beleive that there is a limit of 2GB imposed by the file I/O mechanism used by VFP.
>
>>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.
>>
>
>Definitely not, since I routinely work with larger tables, but the tables and indexes, even though within the record count limits of VFP, can't be manipulated as native VFP tables. I can access larger tables through a backend server as long as no extracted cursor manipulated as a VFP native table, or the associated memo field file, exceed the 2GB limit. I do remember having hit my head on a size limit of a .CDX file in the past.
>
>>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.
>>
>
>This has nothing to do with FAT or limits imposed by FAT - it has to do with the magnitude of addresses usable with internal structures in VFP. VFP encoutners a limit on the available virtual addres space of 2GB, and I'd suspect that this is the real source of the problem, but I'm not a member of the VFP development team.
>
>FWIW, there are file size limits on things other than tables; the table is limited to 2GB (that's the .DBF file - the size of an .FPT is outside of that, as is the size of a .CDX). Even though it's not stated there, there is an absolute cieling on the size of a .FPT manipulable by VFP of 2GB, too If you take a look at the topic Visual Foxpro System Capabilities in the On-Line Help, you'll notice the statement Some capacities may be limited by available memory...
>
>>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.
>>
>
>I think I might have a clue about NT internals...although I haven't written an NT-compliant file system driver other than as an exercise. VFP is not the only language I work in, and I definitely spend at least as much time dealing with system internals as I do with application externals.
>
>>Enough said...let me know if you do find a statement that indicates any limitations on .CDX file sizes.

I did not mean to question anyone's knowlegdge. I simply stated these facts in case your comment where to be taken literally. I know about all the .DBF limits and others, but have never seen any discussions or knowledge base articles specifically related to internal FoxPro limits on .CDX files.

I've yet to come close to any of those limits...so only time will tell...