Re: Connection to dBase file but not using .dbf extentions
From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 08/16/04
- Next message: William \(Bill\) Vaughn: "Re: set parameter value fail?"
- Previous message: haiwen: "set parameter value fail?"
- In reply to: Andy: "Connection to dBase file but not using .dbf extentions"
- Next in thread: Cindy Winegarden: "Re: Connection to dBase file but not using .dbf extentions"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 16 Aug 2004 16:04:00 -0500
On Mon, 16 Aug 2004 19:44:13 GMT, "Andy" <Roonz@Ameritech.Net> wrote:
¤ Hey all, Was wondering if there is another parameter to pass along with the
¤ rest of the connection string to have Jet look for a dBase connection using
¤ something other than .dbf?
¤
¤ Here's my conn string for reference...
¤
¤ "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & cDataPath & ";Extended
¤ Properties=dBASE IV;"
¤
¤ We just happen to use the extension .DAT for all of our database files.
¤
I don't believe the driver will recognize the file with a different extension. There was a
workaround in DAO, by including the file and extension separated by #, but I don't believe that
works with Jet OLEDB and the ISAM driver. Haven't tried it using ODBC.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)
- Next message: William \(Bill\) Vaughn: "Re: set parameter value fail?"
- Previous message: haiwen: "set parameter value fail?"
- In reply to: Andy: "Connection to dBase file but not using .dbf extentions"
- Next in thread: Cindy Winegarden: "Re: Connection to dBase file but not using .dbf extentions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|