Hi Paul,
Just so you'll know, DBFs created with VFP3 and above (now in version 9) are
not compatible with Jet. In fact, DBFs with new data features added in VFP7
and above aren't compatible with the VFP ODBC driver and OLE DB must be
used. The latest FoxPro and Visual FoxPro OLE DB data provider is totally
backward compatible to work with all versions of FoxPro DBFs.
Also, you're right about pointing the connection string to the folder where
the DBFs are, but if there is a DBC (database container, holds stored
procedures, referential integrity info, etc.) then the DBFs are most likely
"contained" by the DBC and the connection string should point to the DBC.
("Provider=VFPOLEDB.1;Data Source=C:\Temp\MyDBC.dbc;")
As you pointed out, in call cases the table itself is only referenced in the
SQL statement itself.

Signature
Cindy Winegarden
cindy@cindywinegarden.com
VFP OLE DB: http://msdn2.microsoft.com/en-us/vfoxpro/bb190232.aspx
VFP ODBC: http://msdn2.microsoft.com/en-us/vfoxpro/bb190233.aspx
> You can use the Jet OLEDB Provider and dBase ISAM driver ....
> Just keep in mind that the Data Source for a dBase file is the folder path
> of the file location The
> filename is specified in the SQL statement (sans file extension).
Paul Clement - 24 Apr 2007 20:41 GMT
¤ Hi Paul,
¤
¤ Just so you'll know, DBFs created with VFP3 and above (now in version 9) are
¤ not compatible with Jet. In fact, DBFs with new data features added in VFP7
¤ and above aren't compatible with the VFP ODBC driver and OLE DB must be
¤ used. The latest FoxPro and Visual FoxPro OLE DB data provider is totally
¤ backward compatible to work with all versions of FoxPro DBFs.
¤
¤ Also, you're right about pointing the connection string to the folder where
¤ the DBFs are, but if there is a DBC (database container, holds stored
¤ procedures, referential integrity info, etc.) then the DBFs are most likely
¤ "contained" by the DBC and the connection string should point to the DBC.
¤ ("Provider=VFPOLEDB.1;Data Source=C:\Temp\MyDBC.dbc;")
¤
¤ As you pointed out, in call cases the table itself is only referenced in the
¤ SQL statement itself.
Hi Cindy,
Yeah, whenever I see DBF I tend to assume dBase. I tend to ignore the fact that these files
represent other database types as well. ;-)
Paul
~~~~
Microsoft MVP (Visual Basic)