>Hi, Michel.
>
>>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.
>
>As Nick said, this can be done. The most famous example of this was the Eurotunnel application, although I don't know if it is still running.
http://advisor.com/Articles.nsf/aid/MATIV02>Going to CodeBase, in any case, would require a major rewrite of you application, as the usage differs a lot from the regular VFP internal manipulation. And I didn't have very nice experiences with CodeBase, although it has been a long time since I last used it.
>
>If rewriting your application data access is not that difficult (maybe you have a properly isolated data-tier), then you can consider going to SQL Server or any other relational database engine. This would not only provide a higher capacity, but also higest security, better consistency, etc.
>
>My two cents,
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
