Hi Jim...

I view this two ways...< bg >..

On one hand, I think the best of both worlds have been combined (VB's integration with windows and VFP's OO capabilities) into .Net. I understand that VFP's OO features are not exactly implemented in .Net, but, it is close. In discussions that I have had with others, some feel that C# may be easier to transition to for the VFP developer. I am not entirely convinced of this. I think VB .Net is a closer match.

On the other hand, given the fact that VB 6 and VFP 7 lie OUTSIDE the CLR, I don't see it as being probable that MS would take the time to invest heavily in combining aspects of two non-.Net environments. Remember, VFP and VB were/are completely different animials. About the only similarity between the two was the language itself. Under the hood, the beasts are different...

HTH...