I consider the question completely legitimate. It's just that I don't have any answers for you. I would be thrilled to see the product climb back up into the forefront of development work. So would everyone else. I just don't believe now is the time to get hysterical about it.

>If that is what you consider what I think is a legitimate question, then I suppose that all our efforts to support a product we work with are all futile.
>I believe all through this thread, the conversation has been about VFP in general, and not all that specific to the upcoming release, which I assume the Fox Team is concentrating on. We (the developer community) have made our living with this product, therefore it is about as important to us as it is the the MS team. In my own case, I am not an incidental VFP user, it is my mainstream, and has been for years. When the product was bundled with Vstudio, it was relatively easy to make performance and ease of development comparisons among the other consitiuent applications. Now that is has been odd manned out, it may well turn out to be the greatest thing since the explosion on the mountaintop, and I hope it is, but I am interested in ammunition to counter the perceptions that are creeping into the fron office, where they perceive that VB/SQL is the future of the database application, when only a year or so ago it was VFP/SQL.
>Defending the current product is laudable, but not really the point of the thread.
>I don't believe any of us are meaning to bash MS, that can be left to others who are more jealous of its market strengths, and not those of us that support the products by using them to develop workable applications in the shortest amount of time, and at a reasonable cost to the client/employer. We are enthusastically awaiting the release of VFP 7.0 and hoping all the mis-perceptions will be put to rest. The performance record suggests however, that this may not be the case, and a legitimate concern is being voiced, no more, no less.
>
>
>
>>As to the Open Letter, I'd more term it a jihad than a suggestion. I was opposed to it before I joined MS.
>>
>>Look, the product isn't even released yet. If you find the same beefs this time next year, then there's room to talk.
>
><snip>
>>>>>>>>>>>>>>>>>>
>>>>>>Do you honestly think that those of us on the Fox Team are actively looking for ways to kill the product? Or to kill it through inaction?
>>>>>>>>>>>>>>>>>>
> The latter is perceived to be happening.