>You mean VB .NET? AFAIK, VB 7 does not exist....< g >

Well, I was referring to whatever it is that is in the following directory on my machine: C:\Program Files\Microsoft Visual Studio .NET\Vb7\VBProjects.

>
>All kidding aside, this is like lobbing a 75 MPH pitch to Barry Bonds or Mark McGwire.
>
>Where do I start....???
>
>1. There is a fundamental paradigm shift between VB 6 and VB .NET. I compare
> it to Fox 2.x > VFP. Nobody in their right mind would run 2.x code in VFP
> as is. At some point, modifications are required. The same is true between
> VB 6 > VB .NET. Using your logic, FPW was forward compatible with VFP.

Well, whatever I said, I do not consider FPW to be forward compatible with VFP. VB6-->VB7 is in exactly the same situation, and possible worse off.

>
>Right, because VB .NET is largely not backward compatible with VB 6. Some code will work, other code - particularly variable declarations may not work. And, if you made use of default properties, you are SOL there too...

Maybe I should have described it differently. VFP.Next will be backward compatible with VFP7 in a way that VFP3 was NOT backward compatible with FPW and the way that VB.NET is not backward compatible with VB6.

But since I was talking about choosing a product now considering how code produced now can be used in the future I used the term "forward" instead of backward.