>Hi Craig and again all
>
>Won't that lead to data intensivity?

That doesn't mean data manipulation. Basically it's store it, retrieve it, add it. Not much more is required.

>I am sorry I guess I was not able to word properly. By VFP core developers I had meant the guys/gals who are creating VFP not us the end-users of VFP. They are the ones who are also helping the .net area for data handling stuff.

And that's a good thing. If the decision was made to move VFP into .Net, then there would be much rewriting anyway, so that is reinventing the wheel.

>Precisely, what does the corner store keeper want from his application and what all hardware is he able to provide. Isn't that the biggest market? Does he require a web app in ASP.net? Does he require VB.net using SQL Server?

The guy at the corner store doesn't care what it's written in or how the data is stored. In fact, he probably doesn't understand any of that. He just wants it at a low cost...and you can certainly get that with VB.Net and MSDE.

>
>We are missing the point here. If I have a huge development company catering to multi-nationals or huge businesses or I am working as a programmer for them then I have to worry about the latest and the bestest. Majority of the developers are small timers getting odd jobs here and there or working for smaller companies. We are being told that we will be able to develop one of the best web apps using the best of RDBMS technology and we are trying to develop such an app for the corner store keeper or that small business. Wow, they'll end up in debt just becuase we want to give them the latest < g >.

How so? There are terrific Open Source products that can solve the problem for low cost or free. If you look at MS products, MSDE is free and VS isn't that much more expensive than VFP.

>
>In fact, I am to call up such a businessman today to get his app done. I got the ref. from a .net / SQL Server developer who is not able to satisfy the need for the app becuase he is going to go overbudget using the latest. We need more .net developers to get our earnings back < g >.

THen you should be very happy with Microsoft's strategic developer products.

>Given the tough rather silly fight I as a VFP developer has had with VB I will go for C# < g >.

There is nothing wrong with that choice.

>I am just an small timer doing small business having small business sense and I am no economist nor an authority so I maybe totally wrong in summerising this. But marketing totally new stuff from scratch will go against the grain. US and other developed countries are facing an outsourcing situation, is it good or bad God only knows. And now we in India and other developing countries are getting an advantage of learning a new language which even the developed country counterparts are supposed to learn so this time it will be an equal fight, now the advantage the developed country developers had over developing countries has been removed. You learn a new language and so do I, you have no experince in the same and nor do I, but I have the advantage of cheaper life-style. Do the math.

I don't buy that arguement. I've seen the facts. While the cost of actual development may be lower than in the US, there are lots of other costs that people don't take into account, making software developed in India and other developing nations as expensive or more so than just having it done by local developers to begin with.