If VFP was part of .NET it would have to share in the CLR and by inference lose its best feature - the local data engine. At that point there is no reason to keep VFP seperate from VB since the local data engine and few other things distinguish VFP from the rest of the pack.

As for .NET and/or Java, that all depends on the needs of your clients/employer. In my case, nothing runs like the Fox and that is where I am staying for now. The .NET framework is very large and will take a lot of time to learn. As time permits I will investigate it, but have no plans to jump into it right now.

Hope that helps.

>Noticed VFP not being included in .NET. Any meaningful reason?
>and is the time to move onto other technologies like .NET or Java has arrived?
>What you think ... ?