>>That's what they said relation to a VFP.Net, not for moving to 64 bits. IMO, I think not having a local engine was not a technical issue, but political (and in big companies, most decisions are political).
>
>Yes - and that was what they fed the VFP community saying if VFP was to go back into VS, it would lose the local database.
>
>That was one of the major threats to make the VFP community decide that VFP shouldn't go back into VS.
>

IIRC giving up macro substitution was another objection.