Thanks Walter,

You are absolutely correct with your views. Yes, it's a business decision rather than a technical one.

Perception of .Net has gained considerably in the last 1 year in India & its difficult to recruit people ( even Freshers ) to work on VFP. We have 4 FPD2.6 developer currently who were all recruited as Freshers.

I have been following your links for quiet sometime. Can you define 'Data mugging' so that I can understand if my application falls under that category ?

SQL-server is not a necessity for the new app. but should be extendable in the future.

Buying a P4 system ( 2.4GHz, 128 MB RAM ) is not a major problem with my Customers. Will VS2005 require a faster system than that ?

At the end of the road, will we ever feel VFP would have been a better solution than VS2005 ? ( say our application is marketable only by 2007 ) ?

Rakesh





>Hi Rakesh,
>
>>>The arguments fore and against are not easily evaluated to wrong or right. It really depends on a whole lot of factors (Yes, current exprience is also one of them).
>>>
>>
>>For someone using FPD 2.6 would you suggest VFP or VS2005 for an desktop accounting software ( upto 15 users in LAN environment ) ?
>
>Well, this is not a simple question. Both upgrading to VS2005 and VFP requires a pretty steep learning curve. If this desktop accounting software is going to use sql server or another database server, VS.NET could be just fine. Accounting in general is pretty straight forward and in general does not require too much of data munging (depending on the data model though).
>
>However if it has to run on modest hardware, uses the VFP database engine and you are used to use xBase style approach, VFP does make more sense from a technical point of view.
>
>Again no straight answers. In fact, technically they both can do, however I'd expect that development in VS.NET will take significantly longer. Further, it seems more like a business decision rather than a technical one.
>
>Walter,