>I hate to rehash but I have to voice my oposition, again. As was discussed in some circles during DevCon, and also here, if we lose differentiation with VB, then VFP will die. And are we also prepared to lose macros? With a CLR-enabled VFP work with DBF's natively? Will it have a command box as powerful as we do today?

I am not talking about losing anything. With a compile time option to the CLR this will differentiate ourselves from VB. We then will be able write "full" VFP apps using the VFP runtime or write VFP apps that use a subset of VFP to conform to the CLR. Best of both worlds.