>
I'm wondering, once again, who you're obliquely referring to here and, if the person obliquely referred to is me, why you're apparently chicken to say so explicitly? Have you no honor, or are you just a coward?
>

There are people besides you who have pitched marketing ideas. When I want to direct comments at you, I have in the past and will do so again in the future.

>
I have told you several times before that oblique references like this will not go unchallenged, and that this challenge will be very expensive to you both personally and professionally. You cannot say you were not told.
>

So your response is to make a threat. Instead of that, why don't you take up the issue and make your case why Fox can be and why it should be marketed and what the probable results of those efforts would be. Personal and professional threats are not productive and will only serve to backfire on you. Don't be so paranoid Steve, believe it or not, everything I say does not pertain exclusively to you. Instead, you could back up your premise with some objective proof as to why your ideas hold water...

>
The utter lack of supporting evidence for your stunning broad conclusions below is notable. Please explain yourself, O great arbiter of reality, O great marketer.
>
>

Lack of evidence? Are you really saying that no objective evidence exists to support the premise that VFP cannot and should not be marketed. It should not be marketed because it would not be cost justifiable. Spending millions of dollars on an unsuccesful campaign is the quickest way I know to end existence of the product. Perhaps 7 years ago, the story would be different. But the fact is, VFP has been going up against VB for all of those years; with lots of help from MS. Now, dotNET is on the scene, Is MS supposed to do an about face and promote VFP over and above dotNET? The only thing that signgiicantly differented VFP from VB was the fact that VFP had a data engine and a languge to go with it. One might think it was the object model and OO. If inheritence was *that* important, VFP would have won out over VB. The fact is, folks can and will get by without inheritance whether they stick with VB 6 or jump to dotNET. Of course, if inheritance is in the box, one would be foolish to not incorporate that feature into the product.

What would the likely fall back position be? My guess is that MS would start with VB 6 and incorproate OO. This is pure speculation on my part, but I think that is what the fall back would be. Pratiucally speaking, dotNET WILL succeed. In theory, it could fail, but in a world where the devotion of money and resources makes a difference, it won't fail. There may be bumps, but it won't fail.

Therefore, if one is reasonably assured that dotNET wont fail and that as well as SQL Server is where MS is focusing its energy as far as dev tools are concerned. The past 7 year trend for VFP is crystal clear. Why you or anybody else believes there is a single upward trend or one that could be created is puzzling. Instead of speaking in abstract and theorhetcial terms, why don't you speak in practical real world terms. Looking at the facts, you will see that such a contemplated effort is an excercise in futility.