Driver can be downloaded here....
http://msdn2.microsoft.com/en-us/vfoxpro/bb190233.aspx The VFPODBC driver is no longer supported
Yes, the driver is not supported for years already but according to OlafDoschke the direct link to VFP ODBC still works. Pavel Celba.
Thanks for updating this, Pavel, but as of now (08/10/2012 13:00 CET) the download is removed. The download link still works. The download link does not work anymore. OlafDoschke
You can still get at it via extraction from the VFP9 Runtime installer you can find at
http://archive.msdn.microsoft.com/foxpro http://www.foxpert.com/download/runtime.html Any of these setups will include the VFP 6 ODBC Driver, I recommend downloading the latest for VFP9 SP2. Extract ODBC by calling with the /X option: VFP9SP2RT.exe /X C:\Your\Destinationdir. You'll find vfpodbc.dll in the extract. OlafDoschke
DEVART company released new set of ODBC drivers for various platforms as Postgre SQL, SQL Server, MySQL, SQLite, Firebird, Interbase, Oracle. They work on Windows, Mac OS X, Linux both on 32 and 64 bits.
Postgre SQL, SQLite, Interbase and Firebird ODBC drivers were tested with Visual FoxPro 9 and worked fine. Other drivers had some problems which will be fixed in a future version.
Here is a drivers page https://www.devart.com/odbc/
You may use the following download links to receive those drivers:
Visual FoxPro ODBC driver for PostgreSQL - (works!)
Visual FoxPro ODBC driver for SQLite (works!)
Visual FoxPro ODBC driver for Interbase (works!)
Visual FoxPro ODBC driver for Firebird (works!)
Visual FoxPro ODBC driver for Oracle (works!)
Visual FoxPro ODBC driver for SQL Server (works!)
Visual FoxPro ODBC driver for MySQL (works!)
Visual FoxPro ODBC driver for SAP Sybase (works!)
New Cloud ODBC drivers for Visual FoxPro https://www.devart.com/odbc/#cloud
You may use the following download links to receive those drivers:
Visual FoxPro ODBC driver for Salesforce - (works!)
Visual FoxPro ODBC driver for ExactTarget (Salesforce Marketing Cloud) (works!)
Visual FoxPro ODBC driver for Dynamics CRM (works!)
Visual FoxPro ODBC driver for Sugar CRM (works!)
Visual FoxPro ODBC driver for Zoho CRM (works!)
Visual FoxPro ODBC driver for Freshbooks (works!)
Visual FoxPro ODBC driver for QuickBooks (works!)
Visual FoxPro ODBC driver for BigCommerce (works!)
Visual FoxPro ODBC driver for MailChimp (works!)
Visual FoxPro ODBC driver for Magento (works!)
Stuff you can and cannot do with the VFP ODBC driver.
- Use VFP data operations like Insert, Update, Delete.
- Referential integrity triggers as implemented by the RI builder are supported.
- There are other supported commands (List?)
- Use views, including nested views.
- CREATE TABLE
- Word97 and Excel97 can read .dbf files, you just need to download the file as described in KB article Q237284 .
- Get column definitions for an individual table, non-parameterized view, or the DBC() with SQLCOLUMNS().
You can join the DBC() to itself to get all column names or index names. e.g.,
SQLEXEC(lnHandle, "SELECT d1.objectname AS table_name, d2.objectname AS field_name FROM DBC() d1 JOIN DBC() d2 ON d1.objectid = d2.parentid WHERE objecttype = 'Table' AND d2.objecttype = 'Field' ORDER BY objectname")
-- Trey Walpole
- You can use default field values across ODBC. I've tested a New Id function call as Default value and a CheckDate(date) rule I had put into a as a field rule. I tested with MSQuery from Excel. -- AndersAltberg.
I have also tested several default values in a remote VFP database which call functions/procedures stored in the remote VFP DB container. Front end was VFP connecting via VFP ODBC to VFP remote database. -- PeterSnowball
- Anything else?
- The VFP ODBC Driver is stuck in a VFP 6-level world, therefore there's no support for
AutoInc field type (introduced in VFP 8),
VarChar (introduced in VFP 9), DBC events (introduced in VFP 7), etc. In fact, you can't access a DBC or its tables at all through ODBC if DBC events are turned on for that DBC.
- No support for DBC or table maintenance operations like CREATE DATABASE, or INDEX ON, or PACK, etc.
- No support for calling stored procedures either explicitly or implicitly. BUT you may call SPs indirectly via Trigger on some temporary table created for this purpose. -- Pavel Celba
You can't use default field values across ODBC. -- Yes you can. I've tested a New Id function call as Default value and a CheckDate(date) rule I had put into a as a field rule. I tested with MSQuery from Excel. -- AndersAltberg.
I have also tested several default values in a remote VFP database which call functions/procvedures stored in the remote VFP DB container. Front end was VFP connecting via VFP ODBC to VFP remote database. -- PeterSnowball
- Use nested views across multiple .DBCs if .DBCs exist in separate directories.
- Use parameterized views -- Mike Yearwood This is solved since the first release of Version 6 of the VFP ODBC driver -- Jos�Constant
You mean that other applications (like Crystal Reports) can open a VFP parameterized view now?
- Store character strings in Memo fields limited to 254 / 255 bytes. -- I have successfully bound a RTF control to a memo field in a remote VFP database. Displayed word files as icons etc. I do not think there is a limitation. -- PeterSnowball.
- Cold Fusion programmers here claim that INSERT requires complete field list for table. Is this what is meant above by failure to support default values?
- Get a list of tables in the DBC using SQLTABLES() - a "Function sequence error" is thrown. -- Trey Walpole
Follow up to this: This may have been due to an older ODBC driver. With at least v.6.00.8428 it works. It may work earlier, but I don't know how much earlier. -- tw
- Data is cached until ODBC connection closes, cannot reuse ODBC connection, see http://support.microsoft.com/kb/261267 , large performance hit
This is only true if VFP tables are the data source. Not true for SQL back ends.
- Use set century to ... You may solve it same way as stored procedures -- Pavel Celba
- Anything else?
What alternate methods are folks using for merging data into Word documents?
Ken Kix: I have decided to "bail" and use an ASCII CSV file instead. My formletter object takes the result of a SQL and (used to) create a table with which to merge. I changed it to create a Cursor, and do a "Copy to xx type CSV". Now I just hope that MS doesn't mess up how Word works with _that_ type of file!
I've been using COPY TO ... TYPE XL5 since Word users typically have Excel and this permits browsing and pre-merge eyeballing, which can be important to some. -- Steven Black
I have also used the COPY TO ... TYPE XL5. The advantage of creating one of these from a temporary cursor vs. a DBF is you can retain long field names (which become column headers in row 1) without having to create a temp DBC. The downside to both of these approaches, I believe, is that memo fields can't be dealt with. I could be wrong, haven't tried in a while. -- Randy Jean
Something else that is odd about Word merges with Excel: This is one of those do as we say not as we do things from Microsoft - If you look at the status messages in Word97 during a merge with Excel you see it is establishing a DDE connection! What's up with that? Don't know if this is still the case in Office 2000 -- Randy Jean
See KB Article Q235357 PRB: FoxPro ODBC Driver Replaced by Visual FoxPro ODBC Driver.(TomPiper passed this along in CIS VFP Forum) -- Ken Kix
Also Q231714 BUG:Cannot Export or Open Linked FoxPro Tables Using Latest ODBC Visual FoxPro Driver (6.0.8428.0)
The help file Drvvfp.hlp can be found in the system directory. Among other good information, this file documents commands not supported by the ODBC 6.0 driver.
One thing I have not been able to do with the latest ODBC driver, is to save the contents of a TEXTAREA to a memo field if the RETURN key is hit anywhere inside the TEXTAREA. The ODBC driver chokes on CRLF's! This is not an issue when using a VFP COM Server like in WC, only through the ODBC driver. has anyone else seen this, What kind of solution is there? -- Harold Chattaway
Have you tried stripping the CRLF's by replacing them with some literal string ([CRLF]) and visa versa at the appropriate times? -Brett
A good solution is to replace the CRLF (chr10) with chr13-Laith
I was able to use the chr function in the sql. Example: insert into mytable (mymemo) values ('this is'+chr(13)+'a test');
Trying the above solution (chr13) gave me extra carriage returns each time I updated the field - For some reason using:
to strip CRLFs all together worked-Mike
Has anyone run into performance issues with VFP ODBC 2.5 driver running under MDAC 2.6? -- David TAnderson
YES! Especially going over a network. Just updated a client to MDAC 2.7 and all seems zippy now. ODBC Driver version is the same. Huh? -- Randy Jean
There is also the OLE DB provider for VFP, available with VS.NET. -- Cindy Winegarden
Is the VFP _ Ole DB _ Provider included in the VS.NET Beta? Has anyone used it? If so, I'm wondering if we will be able to access all the views in our .DBC's - the ODBC driver had problems publishing more than 20 or 30 views in the .DBC - this was always a big problem for us. -- William Fields
See: VFP Ole DBProvider
The new VFP ODBC Driver released as part of the Advantage Database Server Version 9.0 (Beta) is fully compatible with VFP 9.0 Data. You can download the driver from the Advantage website here: http://devzone.advantagedatabase.com/dz/content.aspx?Key=20
The Advantage Database Server has other capabilities, but if you need an updated ODBC driver for VFP, this one appears to work really well and (while the product is in Beta anyway) is free. Posted Jan.2008.
Unless I misunderstand, the Advantage ODBC driver insists on finding a running instance of the advantage server, so you not only have to install their odbc driver, but also their server. Or perhaps I've mis-understood the errors I was getting. -- RickBoatright
You need to configure the datasource as "local server" instead of the default which is "remote". Then you do not need the Advantage server. -- Andy Kramek
You might want to watch this video by J. D. Mullin, R & D Manager for Advantage. -- Doug Hennig
If you set the datasource up to use "local server" instead of "remote server" (which is the default) you do not need to install the server. You don't get the benefits of client/server access, but it is a good starting point. -- J.D.
Another thing to watch out: The ADS ODBC-driver cannot execute any DBC-features like Trigger or Stored Procedures. It also omits Defaultvalues when adding new records.... In short: since it cannot run FoxPro code, everything based on FoxPro-Code doesn't work. thus: Handle with care in a real VFP-Database-Environment! --wOOdy
Help! I'm trying to install the driver on XP SP2. I'm getting Error 1316. A network error occurred while attempting to read from the file C:\VFPODBC.msi. Any ideas? -- Brian Marquis
I figured it out, updating this to provide how I solved the problem. The .msi installer looks for a file with  in the name, in the same directory where you ran it from, so I simply renamed the file. In order for it to actually reinstall, I had to rename the VFPODBC.dll file in my system32 directory. It now works fine, albeit for <= VFP6 tables.
When you are using Windows 7 64-bit if you go to the control panel to add a new connection to VFP you will notice that the driver seems not to be there.
The solution is to use the cpl from this place: c:\windows\sysWOW64\odbcad32.exe This app loads the 32 bit drivers.
Contributors: Pamela Thalacker Mike Yearwood Jos�Constant AndersAltberg PeterSnowball Ken Kix Steven Black Harold Chattaway David TAnderson Cindy Winegarden Andy Kramek
Category Data Category 3 Star Topics
( Topic last updated: 2018.03.03 02:57:41 AM )