>>>>>Thousands of lines of code copying the code back to the fp cursors, and trying to keep all that in sync - then on save building SPT statements. That's right - NO DATA BINDING.
>>>
>>>Yep. Then that developer moved to NET and loudly proclaimed that he couldn't understand why anybody would continue using VFP. ;-)
>>
>>Well, yeah. Kind of like the Mad Hatter's Tea Party. My guess is though he found the compiler and strong typing way too fussy and has been moving on looking for something "more developer friendly" - I hear two autistic schizophrenics in the mountains of Baluchistan are developing a new language that doesn't even require a platform. Moving, moving, moving. Is this what they mean by "mobile application development"? I hear that's the future <bg>
>>
>>Me, I'm stickin' with rockin' the Fox ( in this case, the Golden Fox)
>
>ya I think our Fox is gonna need an AARP card before long. Micro$oft support will end for it the end of 2014 if I remember correctly so I think the days of NEW fox development are pretty much over for us - but legacy apps could go on quite a bit longer, and as we know some of the VFP apps out there are quite large and they'll want to keep them running as long as possible.

Well, if somebody offered me this kind of money to write a WFP EF Prism Devforce C# app I'd be a very happy camper, but there is also some sweetness in being able to squeeze this kind of juice out of Foxpro skills I forgot I had and figured they ranked right up there with stuff I learned in college as a future source of income.

But right now I'm feeling very Fox friendly. <bg> It's like a Cobol shop in 1999.