VB Forum / Database Access / March 2006

Not sure what the problem is.

You can still use CodeBase from .Net using ActiveX/Interopt.

If you absolutely feel you need to downgrade performance and keep to a
managed solution, then just download the latest 'n greatest FoxPro providers
and use ADO.Net. You can also create a semi-"managed provider" with the
CodeBase libraries.

For Ghod's sake don't use ODBC under any circustances (what are you
thinking?)

There are several .Net to FoxPro solutions at the .net website. (MS still
supports FoxPro with its installed based of 12 opposed to VB's installed
base of millions. But I digress. <g>)

hth
-ralph

Hi Miles,

Actually, this is a VB6 forum. The VB.NET forums have "dotnet" in their
names. In any case, I've found your question and I can help.

You can download the latest FoxPro and Visual FoxPro OLE DB data provider
from msdn.microsoft.com/vfoxpro/downloads/updates . It will allow you to
access all versions of FoxPro files from Fox2x through VFP9.

According to the "Sedna Feature Overview" documents mentioned on the
"Microsoft Visual FoxPro Roadmap"
(http://msdn.microsoft.com/vfoxpro/roadmap/) there will be an ADO.NET data
provider for FoxPro in the (codenamed) Sedna time frame (first half of
2007):

2.1 ADO .NET Data Provider for FoxPro
The ADO .NET Data Provider will merely be a wrapper around the VFPOLEDB
provider. This is merely an implementation convenience for implementing a
DDEX Provider for VS 2005. In addition to making it easier to expose things
like the connection control this wrapper will also provide a mapping of
native OLEDB data types exposed by the OLEDB provider to Fox data types.
<<