Loading ad...

Connection strings for DBF / FoxPro

For your foxpro 2.x DBF you do not need to use dBase or Jet driver, check out the Visual FoxPro / FoxPro 2.x section instead and use the VFP driver. Visual FoxPro ODBC and OLEDB drivers work for all Foxpro tables including the oldest foxbase tables and dBaseII, dBaseIII, Clipper files as well.

Microsoft Jet OLE DB 4.0

Type OLE DB Provider
Usage Provider=Microsoft.Jet.OLEDB.4.0
Manufacturer Microsoft


Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\folder;Extended Properties=dBASE IV;
User ID=Admin;Password=;


Type OLE DB Provider
Usage Provider=Microsoft.ACE.OLEDB.12.0
Manufacturer Microsoft


Provider=Microsoft.ACE.OLEDB.12.0;Data Source=c:\folder;Extended Properties=dBASE IV;
User ID=Admin;

Microsoft dBASE ODBC Driver

Type ODBC Driver
Usage Driver={Microsoft dBASE Driver (*.dbf)}
Manufacturer Microsoft


Driver={Microsoft dBASE Driver (*.dbf)};DriverID=277;Dbq=c:\mydbpath;

Remote drives

Driver={Microsoft dBase Driver (*.dbf)};datasource=dBase Files;

SQL syntax example: "select * from \\remotemachine\thefile.dbf"


.NET Framework Data Provider for ODBC

Type .NET Framework Wrapper Class Library
Usage System.Data.Odbc.OdbcConnection
Manufacturer Microsoft

Use an ODBC driver from .NET

Driver={any odbc driver's name};OdbcKey1=someValue;OdbcKey2=someValue;

See the respective ODBC driver's connection strings options. The .net OdbcConnection will just pass on the connection string to the specified ODBC driver. Read more here.


.NET Framework Data Provider for OLE DB

Type .NET Framework Wrapper Class Library
Usage System.Data.OleDb.OleDbConnection
Manufacturer Microsoft

Use an OLE DB provider from .NET

Provider=any oledb provider's name;OledbKey1=someValue;OledbKey2=someValue;

See the respective OLEDB provider's connection strings options. The .net OleDbConnection will just pass on the connection string to the specified OLEDB provider. Read more here.