How about making your transaction history files by month/quarter/year for a quick fix? It sounds to me like you NEED to move to SQL Server - for the long term.



>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