>However, to be fair, Robert has jumped in with a few clarifications now and then. I'd like to see that again, right about now.

Me too, but this issue with VFP and the CLR is probably a smoking gun unlike the past issues with "VFP" not be included in this piece of literature or that. More than likely their putting on the kid gloves for Miami and breaking out their biggest ever smoke and mirror show in order to buy us all off with the other VFP7 advances coming our way (COM+, OLEDB for fox, free threading, etc).

Now in all fairness, if we do get all that stuff we've been promised....

And if all the other tools get rolled into the CLR which will have to inadvertantly cause some major headaches to developers in those camps (can we say backwards compatibility? I hate to imagine trying to recompile something from version 6 in version 7 with a common runtime noose < shiver > around my neck. I foresee lots of existing apps hanging out as version 6 flavor exe's & dll's for quite awhile!)

Might actually might be in our favor for a short lived period of time as far the fox camp avoiding the chaos. "might" being my key word here until we learn more...