>>>>>VFP will be supported until 2015
>>>>>After this how many years do you guys estimate it will still live
>>>>>
>>>>>5, 10 or 15 year
>>>>>
>>>>>Which kind of catastrofe can cause VFP to stop running
>>>>>
>>>>>(sorry, my interrogation mark is gone)
>>>>
>>>>
>>>>I think VFP will be a viable tool until the 2010-2012 time frame. The next major revision of Windows will kill it. It will still run, Microsoft has promised that, but it won't look like a modern development tool.
>>>
>>>It is not a modern development tool now. It is a relic of the x-base heyday. I don't mean to start a flame war, but it had it's time, a good run, was a great development platform, but it will never be a premier development tool again. Its like evolution, species evolve, some die off, etc.
>>
>>It was never 'premier developer platform'. Somehow it managed to outlive
>>(by being able to outdo) meny of those.
>>If you were all that happy with NET (congrats on learing 14000 classes) you would'nt be hanging here indefenetely/beating it on top of our ignorant VFP heads.
>>
>>If I was you, I would be out there making piles of money by utilizing numerous time/cost saving NET features.
>>
>>Time is money! Go out there and make it!
>>Let me (some of us) knit in peace :)
>
>
>All you have to do is stop making unfounded, ignorant statements about a platform you know nothing about and I won't say a word. I am not bashing anybody's head about VFP. I used it for 15+ years. It was a great product, but had its run and is now a relic.

You made ignorant and unfair statement about platform you DO know.
Why is that ?
VFP might be 'xbase relic' to you since you use NET, but that is far far away from truth. You could say that for DOS versions, but not for whole VFP.