>True. But I would prefer to make that choice rather than be forced.

MS is not going to maintain 2 version of VFP so we can have Backwards Compatibility and CLR. They wouldn't even do this for VB!

So "all you want" is a bit unrealistic, if you don't mind me raining on you parade. And the VFP or VB choice is the best option you'll get, cause if VFP goes CLR, you'll have no choice to CLR (except for using older versions of course).

For all I know (and someone correct me if what I know is wrong), VFP going CLR could even force it to give up its local database. Like Ricardo says, somethings we'll need to think about.