>Maybe because we are used to the VFP way of manipulating data - simpler and straigth forward. In .NET you need to do a lot of hardwork and ofcourse resources in order to get the performance you want. In our case, we didn't stick to .NET only, we added INFRA for the UI and MM.NET for the data. Ofcourse, the speed in data software development in VFP is still unmatch by merely 25% vs .NET. But it's worth the investment and effort because of its long term viability.

well we still have to see what 'long term viability' exactly means. Applications written in VFP will be as viable as .NEt applications until 32 bit support is dropped or some other development that causes VFP applications to stop working. True, contract work for new projects would probably not be done in VFP as much and VFP work for contracters would decline. However since there is some 20 years of VFP/FOXPRO applications out there, I'd not expect that anytime soon.

Then there is the problem of new .NET technologies. If I'd adopted .NET 1.0 from the start, I'd probably find myself rewriting data handling parts 2 times now, and with the next version for a third time, just because of the rate of introducing new data handling technologies.

I'm probably going to be a late adopter of .NET (Personally I don't see much value in learning PHP, Java, MySQL), because I Just want to use the LINQ stuff when its properly implemented. It will be a steep learning curve and a very difficult time since timewise I can't afford being unproductive for long. If it was not for a financial reason, it would be because clients would not allow for that.