FoxPro, dBase III, and ADO.NET

  • Thread starter Thread starter headware
  • Start date Start date
H

headware

I have a newbie question about different database formats as they
apply to ADO.NET. I need to get access to a .dbf file using ADO.NET.
The files are in dBase III format. Does that mean I need to use the
FoxPro Data Provider or that I only need to specify "Extended
Properties=dBase III" in the connection string to connect to dBase III
files?

It's my understanding that FoxPro is just one of many programs that
can read dBase III files (just like many text editors can read .txt
files or html files). Is this the case? If so, why would someone be
interested in using the FoxPro data provider?

Thanks,
Dave
 
Hi,

I'm an old dbase/foxpro guy also, and some of my apps convert dbf files to
sql tables, even generate .dbf files when necessary, etc.

You'll need the odbc driver (I believe it comes with vs .net 1.1 but if you
have 1.0 you can download it for free from microsoft.com). The object model
is pretty similar to the sql driver, at least as far as basic routines are
concerned.

But, hey, lose the .dbf format if you can. It's the horse and buggy to sql
server.

HTH,

Bernie Yaeger
 
On 20 Nov 2003 15:16:38 -0800, (e-mail address removed) (headware) wrote:

¤ I have a newbie question about different database formats as they
¤ apply to ADO.NET. I need to get access to a .dbf file using ADO.NET.
¤ The files are in dBase III format. Does that mean I need to use the
¤ FoxPro Data Provider or that I only need to specify "Extended
¤ Properties=dBase III" in the connection string to connect to dBase III
¤ files?
¤
¤ It's my understanding that FoxPro is just one of many programs that
¤ can read dBase III files (just like many text editors can read .txt
¤ files or html files). Is this the case? If so, why would someone be
¤ interested in using the FoxPro data provider?

You can still use the Jet OLEDB provider with dBase III just as you did with ADO.

ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=e:\My Documents\dBase;Extended Properties=dBase III"
Dim dBaseConnection As New System.Data.OleDb.OleDbConnection(ConnectionString)
dBaseConnection.Open()

I'm not aware of any inherent advantage with respect to the FoxPro driver unless you're using dBase
files with a FoxPro application.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top