Michael,

>>A lot of times it is simply because Access is an easier sell as it is a part of the Office Suite. I seem to recall being told some time back that there were indeed measurements taken and compensation paid withing Microsoft based on sales volumes. Don't know for sure if that's a fact but it seems reasonable that this is the case. So, would you rather sell a product that is easier to sell as it is 'bundled' and provides you with more totla gross dollar 'points' or one that requires a higher level of technical expertise to support?
>
>>Not really hard to understand if all of the above prove to be true.

---

>the next logical step then, is to stop developing and selling VFP...

<g>

I'd disagree and suggest that we just get out of the way and let the market decide. It's not really any more difficult than that IMO.

Personally I don't think this product will ever 'die' as some suggest. And, even if it did, who cares? I'm first and formaost a developer who is sufficiently able to learn new tools and the high level skills I've developed over the last 15 or so years of doing this kind of work will be IMO sufficient to allow me to continue.

I guess I just got to the point some time back where I realized that it was not the tool but the person using the tool who made the difference. Think in terms of carpentry... How well are you able to construct a finely finished cabinet? If you're like me you canframe but that degree of finishing capability is beyond you if only for the reason of never actually doing it. Now, how far in the future will people need cabinets? <g>

They will need data-oriented solutions equally as long from where I sit.

Who cares if I use a Makita or a DeWalt saw? I just need to cut. The abilty to make fine cuts does not rest in the saw; it rests in the user of the saw.

FoxPro will live as long as folks are able to 'cut' well with it and I don't see that ability suddenly going away.


>(in the same way we could eliminate cars (for the Green Party); just increase the 'spiffs' on bicycles and create tariffs on cars! Then bikes will total more gross dollar 'points' and won't require the higher level of technical expertise to support.) The only problem is some people need to go further than bikes could take them...
>
>Hey, maybe microsoft should go into the pre-printed forms business and drop all software, can't get much easier, great margins, and no support required!
>
>OK I'm being facetious but, the products are designed for different markets, handled by different business units with different advertising dollars.
>
>Somehow Microsoft has got to learn how to market VFP, it is the cadilac of cars and they shouldn't expect to sell as many cadilacs as chevys. We didn't create the distribution channel for VFP nor do we limit how MS should package or market it. BTW what royalties does MS make on Access? And when was the last time you saw a thread discussing how overpriced VFP was?
>
>One last thing, from your logic Doug, shouldn't they drop SQL Server, or maybe drop Word in support for Works? <bg> Wouldn't dream of it would you, it's clear Works wouldn't handle your needs, Isn't it the same, Microsoft must make it clear about the differences between Access and VFP!
>
>ok, I'll stop now :-\

I'd agree that MSFT should perhaps market VFP more aggressively but they aren't and I'm stillso dang busy I am up on Saturday morning at 2:30 (O dark thirty <g>) doing work.

I'm expecting to have enough work (if our funding goes through - which is why I'm up) to eventually hire some 100 programmers. Not all in VFP and surely not all at the higher levels as we will need 'data translation monkeys' but I can guarantee you I'll do my part in keeping this product alive. Quite frankly I don't really know where I'll find them so I figure to follow the MSFT 'model' of new hires which I think will work.