Despite some of the propaganda going around, VFP to .NET interop works very well and, *IMHO*, I would not say it's inefficent to any great degree. All you have to do is create a few VFP mtdlls, properly call them from ASP.net, and run some performance/scalability tests to see that this is true. Also see http://www.activevfp.com/avfpdemo2/default.aspx for an example...

>The problem with this is that it would not be Managed Code and would involve COM Interop and conversions from one form to another and would therefore be less efficient and slower, and you would still just be working on the .NET side with a DataSet.