Hi There,

Aldough meny will advice you to jump straight to NET,
based on your client base and nature of your system, I wld rather use VFP9.

You should be aware that you hv huge learning/development cycle infront of you any way you turn it. VFP/OOP, aldough built on the same xbase language base - is completely different animal to FPD26. Much more powerfull, but also wild if mishandled.

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.

I remember one VFP gig here in Cyprus back in 1997, where management was firmly insisting on building exclusively C/S solution, that can use DB2,MSSQL or VFP interchangeably. As new on board (and with VFP back then), I did not hv much say in it, so they ended up with solution that was crawling slow - with VFP as backend, and a bit faster with MSSQL/DB2 but terribly expensive for 95+% of their customers.
Result: They were out of the business.

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.

Easier said then done, but make sure that yu offer equal or better functionality and value4money to your cusstomers otherwise they will simple refuse to buy inn.

2c



>Dear Members,
>
>I have been following another thread about migrating from VFP to .Net. But, in my case I want your inputs about migrating from FPD 2.6 to VFP or .Net
>
>Our's is a general purpose Accouting software with about 400 users ( copies ). We are not planning a major change to database structure. It's used by Small enterprises with max 15 users in multi-user mode ( Dbf backend ). We don't give the source code. Customer is not bothered about technology used ( VFP or .net )
>
>Our aim is give a good Windows interface & printing with good ROI ( Volume sales, less cost ).
>
>Advantages of using VFP
> Code re-use ( say 30 % - year-end/reports code )
> Reports - About 450, DOS reports that print to DM Printer
> Familiarity with Language
>
>Disavantages of using VFP
> Lack of trained developers
> Technology obselence ( assumption ) - Like 64 bit, Unicode support.
>
>Advantages of .Net
> Easy availilibity of trained developers
> Latest technology ( Perception of investors, developers )
>
>Disavantages of .Net
> Local cursor processing
> C# - Learing curve & time taken to relases the product ( 1st version )
>
>
>We are already behind market ( still a DOS version ). What would you suggest us to use. VFP or .Net or release a version in VFP & migrate fo .Net ( only if conversion tools are good enough )
>
>Regards
>
>Rakesh