I totally agree with you. I've done a little consulting on the side. If I work with a small company, and am in total control, using VFP is a non issue. But there is a good chance that if you have to get your VFP suggestion past an IT dept, that VFP is a nogo.

And I can see MS' point of view that a lot of effort would have to go into attracting that self employed person. Only to sell 1 copy of VFP.

I'm not sure why companies dropped VFP in favor of VB, but they did in droves.

As I stated before, people are most certainly attacking the messenger in this case. Which is easy to do. But I think in this case, when you are talking about your livelyhood, that the message itself would have much more importance.

PF

>Perry,
>
>>
>>Why people would rip JVP for stating that VFP programmers would be wise to learn something else is beyond me.
>
>
>Like allot of people, I've sat back and read most of these threads the last week or so.
>
>If you were to ask most people here (especially those of us who are not self-employed - and require management buy-in before new development begins) - likely many of them would agree that the argument would be easier suggesting VB-SQL. This is NOT because it is any better or worse than VFP - it is neither - however, decision makers generally make decisions based on what they READ and and what they SEE and what they HEAR.
>
>And by and large, that isn't VFP.
>
>My guess (keyword: Guess) is that the problem isn't so much with the message, but rather the style employed by the messenger.
>
>Just my $0.02
>
>Al