oRox,

>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).

Web Services is the mantra.

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

Yeah, it's good stuff.

>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!)

Have you seen all the hand-wringing over on the devx vb.vb7 newsgroup about broken backwards compatibility, required parens on function calls, changes in array dimensioning, getting rid of set and let, etc, etc...