Kevin,

>Practically overnight many said that .Net is so good and VFP is so bad. The same developers that said many times how VFP was used to build rock-solid apps.
>
>The other thing is that there are only advantages on using .Net and disadvantages on using VFP.

As I mentioned in a previous post, I still think VFP is a great tool. In the classes I teach I have VFP, VB6, Java, RPG, and other developers. When the "other" language programmers try to trash VFP I let them know how wrong they are. VFP developers in my classes are usually well ahead of VB6 developers because they have been working with true object-orientation in VFP since 1995. In addition, they understand databases, normalization, and n-Tier architecture better than any other group.

Something I find exciting is the number of VFP developers who are influencing new versions of .NET to add features that are strengths in VFP. People like Alan Griver (YAG) a well-known Fox personality and guru, hold influential positions at Microsoft--specifically in the area of data access. In addition, MVPs who came from the Fox community such as me, Rick Strahl, Markus Egger, Cathi Gero, Jim Duffy, Rod Paddock, Claudio Lassala, Bonnie Berent, and Kevin Goff help influence new versions of .NET. We know what is great about VFP and want to see these same strengths in .NET. In a number of meetings with .NET teams at Microsoft we have fired up VFP to show them what's great about the product and what we'd like to see in .NET.

I do not believe in blindly converting VFP applications to .NET for no other reason than it's the latest technology. These are the kinds of things I'll be talking about in the seminar. Where it makes sense continue using Fox, and where it makes sense to use .NET--and how best to blend these two worlds.

Regards,