>Robert,
>
>>This was an oversight. I spoke to the person who wrote these pages and he apologizes for any confusion and promises to fix this.
>
>Thanks for the speedy response. Tell them that I'll be happy to help edit the web site for them. :-)

All this talk about Microsoft missing another VFP credit is scaring me. Jobs are becomming harder to find in this language. Are we being forced to learn a new language?

I recently applied for a job where they wanted a VFP deveolper with a minimum of five years experiece. When I get to the interview I was told by the IS director that no new development would done in VFP. Everything created in Fox 2.6 that needed maintenance would be simply recompiled in VFP or rewritten in Visual Basic. They had no intention of maintaining any legacy apps in 2.6, yet, at the same time, they didn't want to face the fact that simply recompiling a 2.6 application in VFP violated all the rules of good Object Oriented programming. Their plan was ridiculous, and I told them so, but they were convinced that Foxpro had no place in their environment. I am finding this more and more lately. VB developers are everywhere, but VFP programmmers are becomming a rare breed.

Is this an active conspiracy at Microsoft? Are we being forced out of our beloved way of life? What's a dedicated VFP programmer to do?