>>I used to be a VFP pro, I switched to c# a few years ago and not looking back.
>>
>>So, I had a tought about this place tonight and I was wondering how this whole thing is still holding together...
>>
>>Back for news... no flame please....
>
>Hi Stephane! Man, Long time no see.
>
>As to your post: Define "dead". VFP has no new features or versions for the past few years however the human body does the same thing by age 18 or so and we live another 60 years.
>
>There's a ton of maintenance and "tweaks" work out there for VFP so the blood is pumping. As to new development, I haven't seen any honestly. I suppose in theory, or in practice I am unaware of, there are legitimate areas where a new VFP would fit a need.
>
>Regarding the VFP faithful and experienced, just my opinion, it's time to move on - err...way past time. .Net is evolving rapidly and very hard to master if you haven't already caught that train. Since VFP is now legacy your VFP skills will always be there if needed but you need to move on to more supported and appreciated platforms for the new projects,
>
>Every serious developer has to be cogniscent of paradigm shifts in our field and roll with them. In 1982 I moved from Apple II assembler to dBase and DataFlex and no one ever asked for my former skills again. The last call I ever had for DOS xBase skills was in 2000 with a Y2K retrofit. I had to tweak a Clipper app in 1998. If I had stuck with any of these skills and ignored the shift I would have been marginalized.

Speaking of those ton of maintenance and "tweaks" work. We already have a Java/Oracle/JSP web version of our tool and for the last 2 years we have been trying to stop development on the VFP desktop version but work keeps on coming even though we do not advertise anymore and I am busy full time on our VFP version for at least the next 3-6 months.