Given Office's market share competition isn't really a problem so I imagine the issue is just to distinguish another new version - and encourage upgrades. Significant difference will probably be the CLR language so .NET seems appropriate.
OTOH there is pretty much nothing about Foxpro that makes it .NET. Putting that in the name would be an empty gesture... and and frankly I don't think it would make a bit of difference.
What will make a difference is anything the Fox team can do to make VFP be seen and used as a tool for SQL Server apps. And I think that is in fact the direction they are taking.
>SNIP
>>A great Foxpro product, named as such, is surely preferable to a badly named product which would be instantly seen as a very bad (no CLR) .NET product.
>
>Charles,
>
>I might debate "...badly named..." but I won't.
>But there is going to be, according to articles, an Office.NET. Now will it be "legitimate" because the (former) VBA will now be CLR? If so, that also seems a stretch, given that most people using Office do not touch VBA.
>In other words, I'd assess the name Office.NET as being by far more of a marketing ploy than a technical accuracy and I wonder why VFP couldn't benefit from the same consideration?
>
>cheers
>>
>SNIP
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
