Jeff,

>>Assumptions from a couple of reporters, that are not based on official Microsoft Press Releases, and do not quote any facts to back up including VFP in the list of CLR languages, mean nothing.
>
>The link was an offical Microsoft Press Release.

Nope. I am certain that you cannot find any MS press release that specifically says that Visual Foxpro will be CLR-compatible. There are several that say something like "all of the Visual Studio languages supporting .NET" or something generic like that, but the quotation you remember as listing Visual Foxpro as CLR-compatible was an article written by a reporter. If I remember correctly, it started out something like "...of course, blah, blah about the VS languages being included, then listed them including VFP.

But you WILL NOT find that anywhere on a MS press release so far, guaranteed.

>Question for you: How long will it take this paradigm shift to be stable enough for implimentation? One year? Two years? How long will it take the majority of companies to begin even thinking about using it? Three years? Five Years?

Well, figure beta in the fall, release in 2nd quarter 2001, first service packs (1 & 2) within the first 6 months, then maybe a crescendo at that point of adoption in enterprises. But I'll bet plenty of test projects will be going long before that for proof of concept, etc.