>>>MS never killed VFP, VFP is very much alive, and will remain alive for many, maaaaany years. The thing is VFP is now an adult, and does not need his mother's support anymore.
>>
>>Until a version of Windows comes along that kills VFP. Could happen in 2015, could happen in 2999. But since MS is not committing to anything more with VFP beyond 2015, the prudent business approach IMO is to act as if that is the retirement day for VFP. It just becomes too much of a gamble to build anything more on it after that. So, the way I see it, by announcing the end of support MS in effect (for practical reasons) actually DID kill VFP as of 2015.
>
>Well, it's your choice, personally I will still be using VFP in 2044, when I plan to retire, at 90. But given the history, and the forces behind SednaX (codeplex), I am willing to bet thet VFP will still work on Windows 3000.

Of course it is an individual choice, and given the maturity of the program, it sure is tempting to hedge your bets and keep using it. You need to do what you feel comfortable with.

SednaX will only work if VFP core works, so it is as vulnerable to "environment shifts" as the rest of VFP.

To use an analogy, as a taxi driver I would not keep driving a discontinued model that may break down any day. As an antique car hobbyist, I would do the exact opposite.


Pertti

>
>>Pertti
>>
>>>
>>>>Nice. Did Calvin say when this VB10 will be available?
>>>>
>>>>BTW, yesterday I talked to a client of mine in a county planning department about VFP's future (trying to maintain full disclosure here, even if it hurts...). Here's a guy who works almost exclusively with SQL server data, and I've written VFP apps against their big SQL server parcel databases. He in turn uses VFP exclusively to query and tweak the massive amounts of SQL data in the server. He looked at me in disbelief and said: "That's INSANE! NOW how am I going to quickly query, analyze and report my SQL Server data?" I didn't know quite what to say, except that VFP will be around for a while longer. And here's but one tiny case study, which nevertheless represents maybe hundreds of thousands of people out there who RELY on VFP to slice and dice and make sense of their data warehouses on a daily basis.
>>>>
>>>>I came away from the meeting thinking "You know what, the guy is right and I'm already jaded. It IS insane for MS to kill this super-mature and easily approachable product! Why on earth would they do that?"
>>>>
>>>>
>>>>Pertti
>>>>
>>>>
>>>>>Okay folks. Everything will be fine now. I just instructed Milind to tell Calvin Hsai to load all the VFP he can into the next VB release. Failing that he could just rename VFP9 to VB10.
>>>>>
>>>>>Also noted - MySQL hits $50 million revenue, plans IPO