Jim,

You make what initially seems like a solid argument. However, the learning you would need to do to be in the .NET arena at all is frar more thqan learning a new syntax for your language.


Here's my thoughts on this issue.

Why might I like VFP to be part of the common runtime group of langauges?

1. So I could leverage the things I already know in VFP.
2. So I could stay within the object model, inheritance ,oedl and containership models of VFP.

The only problem is that if VFP were to become part of the common runtime, it would lose a lot of the syntax that I know and it would most assuredly lose the object model, inheritance model, and containership model because it would need to comply with the common runtime models.

You see, in order to be part of the common runtime you must be compliant with the common runtime rules anmd model and VFP isn't.

If you would like to see some proof of this, just visit a VB forum and listen to the complaints of how VB.NET is completely different from VB 6.