>>The only thing to add to your terms is that whatever it is, it will a relevant feature that will materially boost the worldwide marketshare of the product.
>
>Do you propose a method to measure this?

I am sure it can be done. I think you can pretty much bank on the fact that it wont. If you see MS aggressively promoting the product, that might be an indication. Again, I don't think you will see this.

>
>>Specifically, what you consider to be new and intriguing, will it alter the decsion making processes of the person who is faced with the decision?
>
>If you mean specific design or implementation decisions, yes.
>

No, in the aggregate. Would the tide turn where closed doors become open?



>>Will the new feature make it easier to get into the door that is currently closed to Fox? In the aggregate, I don't think so.
>
>Considering this is amazingly different than what you orginally claimed, I don't think so either. How many technical articles about .NET have you written that just the minds of IT executives in major corporations?


It is not different from what I have been arguing. I have always predicated the argument in the context of the aggregate, since that is the landscape that matters. 5 years from now, there are going to be people that can make a living with VFP. I suspect that number will be less than what it is today.

The fact that you agree that doors are not likely to open that have been closed pretty much settles this issue, at least it should.

As for the number of technical articles I have written, that would be 4 and counting for a magazine with a circulation of over 30,000.