>Ken, I was so disappointed when I over heard you speaking at EssentialFox with a VFP Developer that was asking for advise on moving over to .NET.

I'm not sure what you are referring to. I have never advised a single VFP developer to move away from VFP to anything. What you may have heard is me advising someone who is considering learning and using .NET (with or without VFP) to focus more on VB.NET over C# if they have a chose because it is probably easier to learn and possibly a better investment over time. You never heard me state or advise anyone to move or migrate away from VFP. There is interesting in having people use .NET "with" VFP, they work very well together.

>> >I expected an answer such as: "Why are you dropping VFP?" or "Why not use a mixture of .NET and VFP?" No. Your answer without a split second of hesitation was, "Use VB.NET." At a VFP conference? I could see doing this at a .NET conference. <<

You must have heard what I said to that person out of context. I recall about two people at EssentialFox saying they are required to use VS .NET and not VFP on an upcoming project and they asked a question about it.

>> If you keep doing things like this there isn't gonna be any more VFP conferences because you encourage everyone to use VB.NET. Maybe you should try to encourage the use of both .NET and VFP. <<

Only people learning or using .NET. If you had heard my keynote session at EssentialFox or Prague last week, you'd know that they message is Visual FoxPro "with" .NET. Check out the web site at http://gotdotnet.com/team/vfp with information and resources about VFP with .NET, together. Microsoft is actively working on the next version of VFP code named Toledo which will be a very exciting version of VFP. I hope my reply clarifies your mis-understandings here.