>>
>>I cannot tell you much about NET, but from all I heard, it is even bigger
>>undertaking. Be aware also, that unless you built NET solution connecting to some free database like MYSQL for instance, MSSQL licencing costs just might kill the bird for you! You might end up with the system that nobody is willing to pay for.
>>
>
>>So if you go with VFP9, don't make that mistake eighter. You must hv *economy class* solution that works directly with VFP native tables (lightfast) and also high end solution for those who insist/want to pay for MSSQL. May that be two sister solutions or some smart ntier design, but you should support both.
>
>Will SQL Express not solve the problem of native tables ? ( 4 GB of data is enough for current Customers )
>
>Rakesh

Well if you think that is enough, then it might solve price problem.

If you decide to do it with VFP9 then I wld rather use native VFP DBC,
for that size of app. (By all means chk. buffering/transactions in dev.guide)

If NET is yr choice, then SQL-Express would be more common/natural
*economy class* solution.

Just bear in mind that both SQL/SQL-Express will require on-site installation/maintenance of some sort.