I thought it was an EF Provider, not LINQ to SQL.

>I commented and I'm using it. I'm primarily using it for the ability to project my query results into strongly-typed objects; I'm actually not using too much of the LINQ to SQL stuff it offers (my common use-case is passing in a SQL string w/parameters and getting back a strongly-type collection). 90% of what I'm doing is read-only. I actually mix and match VFP and SQL data so I'll pull the data from VFP but when I need to store it, I do that inside of SQL Server. Tom has been pretty responsive to the issues I've run into. It works pretty well and keeps my code significantly cleaner than dealing with DataTables. Ultimately this is just a nicer wrapper around the OLE-DB driver anyway. So if you run into a problem you can easily drop back if necessary.
>
>If you want something that is probably a bit better tested, I also used the LINQ to VFP provider he wrote. No complaints with it all.