Even more impressive is MSFT's longterm goal with the OS and development enviroment syncronization, and of course, eventually 64 bit.

I use VFP as my day to day tool. The majority of the work I do, I do in VFP. However, I hope I don't anger anyone here but reading some of the posts it is very reminicent of our customers that upgrade their hardware only while kicking and screaming. We have users out there that still use Windows 95 and our Dos-based FPD26 app. As long as it meets their business requirements, no problem. It makes good business sense for them to do so. However, it always turns out that these same customers ask for new features that can only be added to our VFP version. When we point out that the new feature already exists in our new version and that switching to our new version requires them to upgrade their hardware and OS, they are sometimes very angry. They want everything in the original version of our app because they are 'comfortable' with it. They have invested a lot of time and energy learning every single nuance to our DOS-based app and don't want to invest anytime into learning the windows version. Eventually, however, all of their other business apps force them to switch anyway. Most rating programs are either windows based or webapps. Many companies are not longer investing resources into supporting different versions of the same application and we are no different in that sense. We are slowly pulling them along kicking and screaming just like MSFT is us. I can see both sides of the coin.


>>When you don't have to worry about money anylonger, the only thing that matters is your reputation. There is no way dotnet will not succeed (no matter how much $ MSFT has to throw at it). To be fair, their longterm vision is a good one - it is the painful process of getting there that is the problem.
>
>You've hit the nail on the head, not many people are prepared to jump into .Net just yet, a company decision was made here to jump straight in, and yeah, it was painful at first but when you start to pick up the Framework and where MS is actually heading with it, it ain't all bad. The Framework itself has been well thought out, and it's not immediately obvious just how much is there until you start digging.
>
>I think come version 3.0 it will definitely attract more developers, particularly those with a Fox background. Hands up I kicked and screamed when I heard we were migrating, but after 2 years I probably wouldn't turn back, I think C# is nice language.
>
>Kev
>
>>
>>
>>
>>>>Uh oh, this is a troubling post....this really gets people reved up...
>>>>
>>>>I think for VFP's longevity it needs to at least work with .NET and it will with Sedna. I've been using the Fox with .NET web services and its been great. I dont think it will ever become VFP.NET just because of its native database and reporting, unless M$ dumps that stuff.....
>>>>
>>>>My theory is that once .NET gets the cursor engine that VFP has, which I beleive the Fox Team is working on......I dont think there will be anymore additions to VFP.
>>>>
>>>>As to .NET failing, sure it has its shortcomings but with a team of a 1000 developers working on it, and only 10 working on VFP i dont see it failing, also considering the amount of marketing M$ puts into it.
>>>
>>>MS has invested too much already in .Net. It'll succeed no matter what they have to do.