>Mainly you hear it from those who only know FoxPro and don't want to use anything else, ever.

No, I don't believe that's anywhere near true. A convenient generalization and nothing more.
And more than just a tad on the insulting side.

When you've got a tool that lets you do everything you need to do to make good robust applications that serve users well, you tend not to see any need (other than expanding Microsoft's coffers) to move to a whole new parqadigm.

I was happy to move from COBOL to OS/Assembler. I was happy to move from dBaseIV to FoxPro. It tool me some time, but I was glad to get into VFP. I wouldn't mind learning another language. But on my own terms, when I need to (by my own factors) and not because my supplier has cut off development.


>
>
>>I've never understood the "You're either with us, or against us" attitude of many VFP programmers.
>>
>>>Yeah, sure. EPS has been backstabbing the VFP community for quite some time. Marcus got a lot of mileage out of this community, then turned around and made it a business of cannibalizing it. No thanks. I'll look elsewhere.
>>>
>>>>Hello Handi!
>>>>
>>>>You're right, this time will come.
>>>>If you don't want to rewrite all your existing VFP projects and convert them to .NET (C# or VB.NET) instead take a look at the VFPConversion tools created by EPS Software (VFPConversion website).
>>>>
>>>>
>>>>>I know the time will come for us to looking another development tools :-(
>>>>>
>>>>>link : http://msdn2.microsoft.com/en-us/vfoxpro/bb308952.aspx