We have 2 systems (in FoxPro 2.5 DOS, BTW :) which work with data over 2 GB. One was designed this way 3 years ago ( don't ask ME why it still is in FoxPro 2.5 for DOS :) The data are split over multiple tables, plus there is a lookup table that keeps the policy number and reference in which table the data are for faster access.

Another system's transactions table just approached 2 GB limit last year, and was kept afloat for a while by removing the unused fields until the necessary changes were done to split into multiple tables and fix about 200 programs. :)


>Hi everyone,
>
>I never thought to see the day, but now it is happend. I have a client who is pushing through heaps of stuff. and now I am facing the 2GB problem. Aside from breaking up the tables (which is going to be a pain), or upsizing to SQL (not a near term solution), is there anything suggestions?
>
>Background: Currently in VFP6SP4. Issue is affection finance transaction table history file. They run a 'period close' (like a monthly statement) and the current period data gets shoved into the history. However, although we have been routinely re-routing the history table, the current period table is now rapidly approaching the 2GB barrier.
>
>TIA
>
>Ric