>Re specifics: KL has nominated some field types, most notably the new XML field type, that VFP will not be able to use.
>
>I agree with Simon Clark that at the very least VFP should be able to pull incompatible field types into a memo field. I don't care if feature sets are "locked down"; unless this is addressed, JVP's previous assertion about VFP's obsolescence becomes unarguable. It is a truism.

I never said that Europa would not be able to map the Yukon XML data type to a VFP memo field. I said that VFP would not support the XML data type natively, there is a difference.