>Yeah, I will check those out. I've alway been impressed with what you've done Rick. Do any of your tools use ADO.NET as a middle tier between VFP and SQL ?

No, not directly. I would think that if you want to go through .NET you'd build your own middle tier otherwise you end up with something that is mediocre at best in performance.

I have built some tools that allow you remote data access via a Web server, using SQL Server as the backend. It's a REST SQL front end to SQL server along with client classes for FoxPro and .NET (and anything else could be easily built as well). Not quite what you're looking for, but possible. It'd be possible to build this out to actually serve data directly as a COM object rather than through the XML middle man.

As far as I see it though - there's little reason to build a generic data layer in .NET to be called from either VFP or some other COM client interface. it's possible, but the overhead for this would be too high IMHO. There's no really clean way to convert data between VFP and .NET (short of CursorToCollection or CursorToXml, both of which have tons of overhead). Likewise .NET data usage in FoxPro would also be pretty slow for the same conversion reasons.

If there's no other way - yes it's possible but as a serious long term business solution: no :-)

+++ Rick ---