The Classic VB may have fazed out, but look at the job ads. Still many VB6.0 position available.

Now, I'm not saying to go out and learn VB6.0... :)


>>7+ years ago - when that question was asked - it was clear that VFP was not
>>nor would it ever be part of MS's strategic focus. It was at that time, I
>>jumped off the "VFP Bandwagon".
>
>7+ years ago, VB seemed to be the answer and VFP soon to be dead. But what I find ironic is that right now, it's VB which is dead (VB.NET is not really VB but .NET with a VB syntax) and VFP is still alive and relatively well. OK, .NET is crushing every other development tool on the Windows platform (even the excellent Delphi) and if .NET 2.0 fulfill its promises, maybe it will be the time for VFP to enter in "maintenance mode".