One problem can occur: VFP ODBC driver is derived from VFP version 6 and it does not recognize tables containing autoincremented fields, varchar, varbinary, and blob fields.
VFPODBC WINDOWS SERVER 2008 INSTALL
The lates VFP ODBC driver is here: So download it and install and Access will allow to link DBF tables as external data. You have VFP ODBC driver on your computer already but the old version which is not suitable for MS Access 2007.
You have to code in VBA to use VFP OLE DB which is probably not what you intend to do. VFP OLE DB provider is something else than VFP ODBC driver. I've attempted to configure this via the ODBC Data Source Administrator. I've a piece of third-party software that requires the Visual FoxPro ODBC driver. Visual FoxPro ODBC Driver Installation & Configuration. Home Newsgroups > Windows XP > Windows XP General. I noticed the driver list has more than one FoxPro driver: Driver para o Microsoft Visual Fox Pro 1.00.02.00 VFPODBC.DLL Microsoft dBase VFP Driver (*.dbf) 1.00.02.00 VFPODBC.DLL Microsoft FoxPro VFP Driver (*.dbf) 1.00.02.00 VFPODBC.DLL Microsoft Visual FoxPro Driver 1.00.02.00 VFPODBC.DLL Microsoft Visual FoxPro Driver-Treiber1.00.02.00 VFPODBC.DLL I tried to create a machine dsn using Microsoft Visual FoxPro Driver and got the msg: You must first install the current version of the Visual FoxPro ODBC Driver. In MS Access 2007 I used External Data tab/More/ODBC database to link to a File Data Source.
I downloaded the ODBC driver, vfpoledb.dll into the folder C: Program Files (x86) Common Files System Ole DB from the web link The download link on that page is VFPOLEDBSetup.msi. I'm trying to use an MS Access 2007 mdb to link to a Visual FoxPro dbf file.
0 kommentar(er)
