Interesting. IMO, you should continue to do it that way.

>I've actually written my own VFP class that chops up the data and uses http to move the data back and forth between the desktop app and web com. It's been in production for a number of years now and works really well.
>

That will add unneeded code, layers, and problems. You're betting off using a VFP component to read SQL Server and then use your existing transport mechanism since you want to keep the same architecture.

>The other thing we are looking at is LINQ. It looks like we could create a middle tier COM with this that VFP could instantiate and call. Then this LINQ COM would use ADO.NET to talk to SQL instead of ODBC....