>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

Rakesh,
A few cents:)
If you have never done a VisualFP app before you need a learning curve. From fox2x to VFP it's not just few days/weeks and even months IMHO.
I don't say go with VFP or .Net:) Only you could decide that yourself. At least now .Net express versions are free, you could download and test them yourself say at nights (no money earning in that period-just for yourself). You'd have pain I guarantee but that pain might turn out to pleasure in time especially if you can teach yourself to think in object terms rather than relational data:) You might even be surprised it's now easy to create a (simple) form in 1-5 mins both in VFP and .Net. Though I'm a foxhead I should admit .Net is now ahead (but initially you'd really have pain when dealing with data - too much accustomed to work woth relations).
PS: I don't mean one is better than other. I don't make such comparisons. I chose C# in .Net family if you wonder (and trying to add IronPython recently).
Cetin