Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
FoxPro 8.0 and File Sizes?
- Thread starter Redsz
- Start date
- Thread starter
- #3
Redsz,
You caught me just as the phone rang, which is my excuse for such a terse answer. The explanation from the Fox Team as to why this will NEVER happen is that there are just too many places in the code where this limitation is assumed or even explicit. It's part of the OS record locking scheme, the offset links into memo files, and others have been mentioned. If it were changed then the tables / indexes / memo files would no longer be compatible with previous versions of VFP (and other applications that currently access them). And we'd have to deal with yet another .DBF variant! <s>
There is also speculation that MS marketing has nixed this even if it were technically possible - they don't need anymore "free" competitors to SQL Server. There are other DBMSs like MySQL that can handle large data files, and of course a good design can allow very large data sets with "partitioned" tables (see for a discussion on this topic).
Rick
You caught me just as the phone rang, which is my excuse for such a terse answer. The explanation from the Fox Team as to why this will NEVER happen is that there are just too many places in the code where this limitation is assumed or even explicit. It's part of the OS record locking scheme, the offset links into memo files, and others have been mentioned. If it were changed then the tables / indexes / memo files would no longer be compatible with previous versions of VFP (and other applications that currently access them). And we'd have to deal with yet another .DBF variant! <s>
There is also speculation that MS marketing has nixed this even if it were technically possible - they don't need anymore "free" competitors to SQL Server. There are other DBMSs like MySQL that can handle large data files, and of course a good design can allow very large data sets with "partitioned" tables (see for a discussion on this topic).
Rick
Mike Lewis
Programmer
Redsz,
If the 2 GB limit is a problem for you, you could always consider splitting the table into two "vertical" parts: half the fields in one and half in the other, with a one-to-one relationship between them.
Or, you could move to SQL Server.
Mike
Mike Lewis
Edinburgh, Scotland
If the 2 GB limit is a problem for you, you could always consider splitting the table into two "vertical" parts: half the fields in one and half in the other, with a one-to-one relationship between them.
Or, you could move to SQL Server.
Mike
Mike Lewis
Edinburgh, Scotland
- Status
Similar threads
