>After reviewing this thread and speaking with another VFP developer, I'd have to agree with Mr Strahl. I get the sense that one of Ken's goals is to convert VFP developers to VB.NET. I've never seen a Product manager so excited about another product and so enthusiastic to promote it. Should we also consider porting to Access?

My comments about VB .NET were simply addressing those people who have stated they are learning or using VS .NET, it has nothing to do with VFP or strategies around VFP. VFP and VS .NET work well together as I demonstrated in many areas in the keynote session at EssentialFox and you refer to whitepapers, examples, and video clips on this at http://gotdotnet.com/team/vfp. I'm excited that VS .NET, especially ASP.NET, works well and adds value to many VFP applications and that MSDN subscriptions are a great deal for obtaining the best tools for these types of solutions. There are not goals to get VFP developers to move away from VFP, but for those VFP developers learning and using .NET espeically with VFP, there is some information being provided to assist in that plus MSDN subscriptions as a discounted way of obtaining the products. If you have any other questions or concerns, please let me know.