>>Ohhh... it seems they're passing the burden to us. Why the need for a dialog first?
>
>>Wait a second! This is what made FoxPro great back in teh 2.x and earlier days (as far as I can tell from discussions with folks like David Anderson, before my time of course).
>
>You missed my point. MS Team knows CLR and .NET technology better than us no matter how expert we are in VFP (exclude me anyway).

Actually, they don't. They know how VFP works, they don't know the work that we do with VFP like we do. And believe it or not, they don't use VFP as much as we do. When's the last time you told your clients what they wanted? How did they respond?

>Are we in the better position to say that CLR is a necessity or not?

Yes. If you have done your homework, then you should have a pretty good idea what .NET and the CLR are, and how they will fit into the picture.

>At this early, no VFPers would safely say that CLR is NOT a necessity thing.

I disagree.