Maybe it will..maybe not. Apparently some of the problems are in the designers in .NET. They were built specifically to handle SQL Server and Oracle.

Also, keep in mind that the VFP 8 beta download does not have the final version of the OLE DB provider. There could be updates to it before release.

>I have seen numerous posts regarding VFP oledb's driver and it's lack of
>schema information. I have also read info on people who have tried manually
>defining the primary key for command builder but still failed. There still seems like there in no easy way to update a Foxpro Table in Dotnet
>
>I have 100+ dbf files, I cant be manually writing update, Insert and Delete
>routines for all the dbf(s). It seems to me that if I can point to the primary key, or manually define the schema then the rest of the Ado.net's auto SQL generation puzzle should work.
>
>I have successfully used ADO 2.6 with foxpro tables under VB6 with no
>problems. The recordsets knew how to update the data, why does ado.net only support these "Disconnected" recordsets.
>
>Where is the VFP team in providing a newer driver. I expected VFP8 would of solved the schema problem.
>
>Am I missing something?
>
>Thanks in advance.
>Mike Pisano