Perhaps a good application framework will help. But whether you choose .NET or something else, you'll have basically the same issues. Learn the new language, rearchitect, rewrite. If you choose .NET, you may be able to move parts of the application at a time. The Interop Toolkit may help. See http://www.craigberntson.com/articles/articles.htm. This may help too. www.vfpconversion.com

You may want to ping Bob Bartel who comes here from time to time. He's in the process of rewriting a VFP app into .NET.

>I think that is a given, but the real question is what will provide the easiest learning curve and allow me to create a "new" product that is superior to the previous one. From my incomplete analysis of .NET, it looks like I will spend a great deal of time learning the product, then spend even more time re-writing (even more than the initial development time in vfp) and "maybe" end up with a similar product. Where's the payoff?