>It's hard to not notice that **nobody** commenting on the VFP EF Provider is using it!?!? Eventually, like Lewis and Clark, you will make it to somewhere but if by chance one day you find yourself thrashing around in the bushes you will be a testament to the "bleeding edge". I stay with ODBC or OLE DB and limit my exposure to their weaknesses. It may not be elegant, but then on the boulder to boulder level neither are the pyramids. Just my 2 cents.

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.