Mike,

Well stated.. There's no reason whatsoever for this kind of panic or sense of helplessness. We need to think with our brains, not our emotions...



>>So we're giving up. The VFP ship is now sinking... Time to grab a life jacket... What will happen is every MS product in ther near future are .Net except VFP.
>
>1. First of all, I never said give up. I did suggest considering logic to make your decisions instead of faith.
>
>2. The VFP ship is not sinking. Same reason the Delphi, and Java, and Linux ship is not sinking. You think that VS.NET will single handly wipe out everything thats not VS.NET? Of course not.
>
>3. VS.NET is a tool to build web services. VFP7 can build Web services. We are not being robbed of anything substantial. You say the CLR? Well, its just a runtime, and we already have one (and I think it works pretty damn well). Yes, there are some more technologies down there, but when it comes down to it, Jess, the future is Web services, written in any language on any platform.
>
>4. Do you think that creating a VFP.NET will encourage hoards of people to switch to VFP? I think that if we moved to VFP.NET, existing VFP develoeprs woudln't be any better off with VFP syntax than C# syntax. We'd have to work with ADO.NET, ASP.NET and the .NET framework. We'd also be thrust into a new IDE and debugger. We would gain NOTHING and loose an awful lot of people in the transition.
>
>5. Finally, when it comes right down to it, nothing will last forever. Keeping VFP around in its current shape mean it will have a purpose. Trying to take it to new grounds by bandaging it up so it can compete with elegant built-from-scratch languages like C# is pointless, and will do us no good.