>>As to "what would the difference be between VB.NET and VFP.NET?", I think you must have misunderstood me. What would be the difference between VB.NET and VFP? Plenty. Nothing changes when you simply rename VFP to VFP.NET, and that is all I'm suggesting. Europa wishlist? OK, that's better than nothing, but I ask again "why wait?" I would gladly postpone the release of VFP 8.0 however long it takes for them to reprint the boxes, or whatever it takes to make the switch. One thing is for sure, they don't have too much promotional material to rewrite! ;-)
>
>Well, that's also another alternative. Switching the name would give more recognition. If the product is so well ready for .NET integration, then, lets reflect it in the name. There you go.

Michel;

Remember the term “CodeBook compliant”? Make that VFP .NET Compliant and the word Complaint should be in 4 point type! :)

Tom