Hi Martin

>In any case, VB.NET is for me something more debatable. It was supossed to be there to drive the millions VB developers to .NET but wasn't very succeful at that.

I guess the mistake will not be repeated in VFP's case. Keep VFP as a pure language for a while. Give it superb interop. Add as much, all of it, into a similar language or create a new language (name atleast) in .net with all the VFP stuff (repackaged), then the transition will be very easy in 15-20 years time.

The new (repackaged VFP) language will satisfy a lot of egos who don't want to use VFP just becuase of all the rumors.