Craig,

AWESOME! [standing ovation]!

You have a wonderful gift with words. I've bookmarked this entry.

Bottom line for me (and I think much of the VFP community): I'll be happy to move to .NET when Microsoft has a .NET product that's better than existing alternatives. I'm looking forward to this day as I'm always looking for better tools to deliver my products. But in the meantime ... why would anyone in their right mind upgrade to a new platform that offered less (in terms of features that they USE on a daily basis) AND then painfully rewrite an existing code base to create a product with less features? Where is the business sense in this strategy?

As you said Craig, ASP.NET _IS_ usually a better alternative than a VFP based .NET solution so it makes sense to use. BUT ... I still think .NET misses the boat (by a significant margin) for a desktop client based solutions. Rick Strahl does a great job explaining this issue (re: why his Help Builder software remains a VFP product) on his blog as well as in the recent issue of FoxTalk or FoxPro Advisor. And Microsoft demonstrates this strategy as well as they continue to release the majority of their software (Office, Longhorn) based on non-.NET code.

Malcolm