>You are also correct in that VFP is for the most part not being taught in schools. Too bad since its local data engine could probably make learning easier, but that indeed it is a hard fact. As a result by inference yes there are hints to go and learn something else. That something else may
very well be VS.NET for me sometime in the future...

We have worked with some schools to get VFP in classrooms, but generally the attendance results are too low to maintain it. Just like people asked to have more VFP at conferences like TechEd, and just recently VFP had sessions at the Microsoft PDC conference in Brazil, and only 20 people attended those sessions which in the end is too low to justify it there. Fox developers generally attend Fox related sessions and in general.

These are not things I have to mention or talk about, but to me being open and honest about efforts and expectations is what I think VFP developers need and deserve. I know some VFP developers may not like to hear me talk about VS .NET with VFP, but in reality they do work well together and often IT managers and decision makers need to hear and understand that in order to keep VFP development within their company.

A good sell of a modern application may well sell well built using VFP7 with SQLServer2000 as the database and ASP.NET as the web view/update system. If people do have problems simply building VFP stand-alone apps, adding things like ASP.NET and SQLServer to their toolkit and saying more about being an MSDN developer vs. a VFP developer may end up opening opportunities and/or increasing hourly rates.