>Does this mean that Sedna will include a native VFP provider for ADO.NET? Or does the "DDEX" mean that a component will hook into the OLEDB driver, but provide better integration with VS.NET?

DDEX is just the Adminstration layer that's used by Visual Studio and the server explorer. What this means is that you will be able to design your databases through that interface in VS.NET.

I'm pretty sure in talking to Melind a few days ago that there won't be a native ADO.NET provider. Frankly I don't think that would buy you a whole lot anyway. The big problem with the OleDb provider is that it doesn't very well support iterative and EXCLUSIVE operations which makes administration of a Fox database through OleDb (or ODBC for that matter) nearly impossible. Using a native ADO.NET provider wouldn't change that although you might get better performance if done right. Perf however, isn't a big issue with the OleDb provider - more than anything it's little type incompatibilities and the lack of admin functionality.