Some other (DB) systems allow you to have multiple 'fragments' for a data file (e.g. Omnis) - i.e. overcome the file-size limit by having additional physical files for the table which are used transparently when accessed. However, this won't get over the 4-byte index offset limitation...

I'd be interested to see any articles on methods for using very large tables - a n existing program I have looks like it will exceed the 2Gb limit soon.

>I suspect that MS isn't going to change the 2GB native file size limit in the near future, since it'll probably affect some of the underlying low-level file handling, and the size of things used to represent offsets in a file (right now, at 2GB, a signed integer of 4 bytes length can represent an offset; bumping it from there would change every data structure that contained an offset within VFP at a minimum.)
>
>You're free to make the request, though; it just happens that there are good, pragmatic reasons for the limit in this case. We'd lose a great deal of backwards file format compatibility with this change, since now, more than just the headers of a VFP(n+some value) table would be affected.