>>
>Because you can do the .NET way in VFP also. But as a bonus you have several other ways in VFP you don´t have in .NET. This make VFP a more flexible tool and enables you more to solve a problem according the logical solution.
>>
>
>Interesting "logic"...
>
>
>>You´re a VB/.NET Weenie who cannot stand beeing wrong..
>
>At least the VB/.NET weenies of the world won't have issues finding work.

There are definatly more VB jobs that VFP, of course there are more VB developers than VFP. I also think that every 12 year old script-kiddie thinks they're a VB programmer and that overall the professionalism among VFP programmers is higher.
As far as finding work - being one of the better programmers in whatever language(s) you're dealing with can be just as big of factor to the number of jobs. If there are 20,000 VB jobs out there but you don't know VB very well, work slowly, can't do analysis work, just overall stink - you're not going to have much luck finding a job (or at least keeping one anyway). On the other hand, if there are 200 VFP jobs out there and you're a top notch VFP developer - you're going to get one of those 200. A good example of this is a guy I know who is a UniData/Pick programmer. Not to many PICK jobs out there now is there? Well he's always been able to find a job - why? Because he's one of the best PICK programmers alive. Probably not the smartest carrer move - but if he is happy & employeed so be it.