John,

I promised myself that I'd interfere in any subsequent negative statements that you feel yourself compelled to make about VFP's future, so here goes...

1) This was addressed to KenL, not to you. Yes, you have every "right" to reply, but it should also be most clear to you that your position on these matters is now extremely well known throughout the UT. There is no need for constant repetition of your view, save your own objectives.

2) You are one of several who, on various topics, feels compelled to answer on behalf of Microsoft. This does us all a huge disservice! Whether it be as regards the future of VFP or the plausibility of adding specific features or improving bug reporting about VFP or a host of other things, only Microsoft knows the true story! Instead of stepping in to provide some plausible explanation/stand/excuse for Microsoft please (you and others) let Microsoft speak for themselves!!! That way, IF they reply we can get at the accurate answer and if they choose not to we can infer certain things for ourselves. The latter may well be fodder for additional discussion, once it is allowed to happen.

PLEASE... we all know your position on the future/decline of VFP. Let others, and most especially Microsoft, express contrary or confirming views.

Jim

><<
>what can we do as VFP Developers to help you market the tool to bring VFP to a decent level among non VFP users and/or Microsoft????
><<
>
>I think this is where you may be missing the point. MS, as a stated policy by both Ken and others at MS, do not wish to grow the VFP market. i.e., MS is not interested in converting non-VFP users to being VFP-users. Instead, MS wants these people adopting VS .NET.
>
>As far as keeping Fox alive as far as new features are concerned, the only thing you can do is to continue to purchase upgrades. Again, this has been stated by Ken on numerous occasions.
>
>MS has neither asked for, nor does it want the marketing assistance of the VFP developer base. FWIW, as long as MS continues its push toward a VS .NET dominated development world, there is nothing on a significant/material basis the VFP development community can do as far as marketing is concerned.
>
>IMO, the VFP community has read and continues to read too much into what Ken promised. Somewhere, people made the leap that Ken's efforts in educating the non-VFP parts of MS translated into promotion of the VFP product. Nothing could be further from the truth. It is a very fine line that is being walked. On one hand, MS does not want to promote the product. On the other hand, MS wants happy VFP customers. There is no reason to kill the product. There is no reason to promote the product. The people that MS encourages to use the product already use the product. On a long term basis, this is not sustainable. Markets grow or die. There is no third direction. Eventually, the issue will take care of itself. Enough VFP developers will have made the transition to another tool (MS hopes VS .NET). This in turn will mean less people will upgrade to a next version of VFP. Eventually, the product will not warrant new development and the product will go into maintenance mode. It is not a matter of
>if, but when. And FWIW, VFP is not any different from any other product. The difference is where VFP currently sits in the product life cycle. VFP is a mature product, eligible for membership to the AARP and gets Modern Maturity Magazine. (Ironically, the AARP is one of, if not the most influential lobbying groups in the USA!) IAC, all the videos, banners, awards, etc, while they do good for the feel good factor, won't change the overall landscape of VFP.