You can use ODBC in .Net to talk to SQL Server, but ADO.Net will give you better performance and memory management. But using COM, you'll lose some performance on the VFP side. I'm just not clear on why you don't use ODBC for the VFP components and ADO.Net for the .Net components.

You also say "ASP", but I assume you mean ASP.Net

Have you read the articles on Rick Strahl's site about .Net/VFP interop?


>Well my method only talks between VFP tables locally and at the web. I will still need to implement a method to talk to SQL.
>
>> Interesting. In my opinion, you should continue to do it that way.
>
>The reason I'm considering something like LINQ or even .NET is for two reasons. One is that we also have to write code for our ASP pages to talk to the same SQL tables so these COM methods could be called from both VFP and ASP. And two, our understanding is that .net doesn't use ODBC to talk to SQL but ADO.NET which seems to be a better choice? Do you have any insight on that?
>
>Once again Craig, thank you very much for all your help and input over the years. As always, it's very much appreciated.