Thanks for the reply. I think that we will do the same here instead of using codebase.

Michel

>>Hi
>>
>>We have very large table. We are very close to the limit of FoxPro (2GB). Soon we have a project that will make that table will be bigger. We are thinking about partioning data or use codebase. We want to make the best move. I wish I can have the opinion of people who did the same move before.
>>
>>Michel
>
>I used the partitioning of data in 2 projects already.
>
>The data were split between several tables with enough space in each table to grow for the next 30 years. All records related to the same entity (say, insurance policy) are stored in the same table. There is a lookup table that tells you in what data table the given policy records are located. For simle SQL statements against the policy such distribution even increased the data handling speed. For the queries against all database there is a procedure that issues the SQL statement against each data table and then combines the results into one result set.
>
>In one project the data were designed that way from the beginning, in the second one this kind of data distribution was implemented for a huge financial transactions table. That required to change about 200 programs in the application. (yeah, as usual - everybody thought that the app will not work that long to fill up all 2 gigs :)