Daniel,

>Doug,
>
>> The difference In my opinion is that Microsoft is in a far better position
>> to guage the reality of the presumptions. In other words, their sales and
>> marketing factual information v your observations with your circle of
>> developers. In other words, their vantage point is better...
>
>... but they do miss the boat at times.

Oh, good heavens yes..

>
>Is VFP losing or gaining market share? I don't know what's VFP position
>in your mnarket, but VFP jobs in Richmond are fast becoming a thing of the
>past.. It's not going to affect my job.

Honestly don't know Daniel. Candidly I have at least 2-10 years of VFP work on my desk as I type..

>
>The main problem I face when trying to sell VFP as a development tool is
>managers perception. The general perception is that VFP is playing catch
>up to th other tools and thus not worth using. VFP7 adds Intellisense, VB
>had it for years... VFP8 adds AutoIncrement, Access had it for years...
>You see the pattern.

Well, my take is "who cares?" Either grow your skill sets or find work elsewhere.

>
>AutoIncrement has its place but it's not big deal to most developers that
>currently use the product and it certainly won't be a selling to me or
>my client managers.

Well, let's give you this point then. IMO this doesn't change the bottom line. Good developers will always survive - because they are good. I focus on improving my skillset all the time and I've managed. <s> I sometimes get the impression that there are some out there who think that VFP work or the continued life of the product is some sort of entitlement. IMO it is neither. While the sun is shining I'll make hay, as they say.