Install the Microsoft VFPOLEDB Provider on Windows 8 64 bit

Posted on 2014-03-01
Medium Priority
Last Modified: 2014-03-02
I've searched widely and tried anything I can think of to install the VFPOLEDB provider for VFP on my new Windows 8 machine with no success.

I downloaded both the MSM and MSI files from http://www.microsoft.com/en-us/download/details.aspx?id=14839, ran them as Administrator, the installation appears to run just fine, but when I try to access data from my application I get an error that the OLE DB provider is not found.

I have installed the provider before on other Windows 8 computers which I now suspect may have been 32-bit, as I did not have any difficulties with them working.

I also have it working on my previous workstation, which was migrated from Vista->Win7->Win8 and is running 64bit. It had been installed somewhere along the way during my use of the computer...

What do I need to do to get this installed and working in this environment?
Question by:Maritimed
  • 2
LVL 43

Accepted Solution

pcelba earned 2000 total points
ID: 39897453
MSI file is the right one to install. MSM is a merge module which you can add to your own installation packages.

"when I try to access data from my application I get an error that the OLE DB provider is not found"

This sentence says a lot... The application is 64 bit probably so it cannot see the 32 bit VFP OLE DB provider.

You have several options:
1) Compile your application for 32 bit environment
2) Try to find 64 bit data driver. If you convert your data into dBase DBF then Office 2010 offers 64 bit driver. (Note: This driver was removed in Office 2013)
3) Sybase advantage server also provides 64 bit DBF driver bit I did not succeed to use it together with 64 bit MS SQL Server a few years ago... (More info: http://www.sybase.com/files/Data_Sheets/advantage_ODBC_ds.pdf)
4) Lianja (http://www.lianja.com/) also supports DBF format but I am not sure if the Lianja ODBC driver could help in your case.
LVL 40
ID: 39897543
Microsoft Access through OLEDB has the same problem on 64-bit computers.

As stated by pcelba, compiling the application for 32-bit solves the problem with Access, and I suspect that it would do the same for FoxPro.

If you are unable to compile, you might try to run the application in compatibility mode for an older version of Windows. Since older versions did not support 64-bit, I suppose that the system adjust for 32-bits when doing so.

To run in compatibility mode, you need to locate the .exe on the hard drive (not a shorcut), right click on it and select the Compatibility tab. Note that in order to enable compatibility mode for XP, which was the last officially supported OS for FoxPro, the application needs to be installed in Program Files (x86).
LVL 43

Expert Comment

ID: 39898397
Just FYI, the last FoxPro SP hot fix was released in April 2009, so the last supported OS is not just XP... VFP OLE DB provider is a little bit older than above mentioned hot fix.

OTOH, FoxPro is a C++ application based on Win32 API Windows subsystem so it should run under each OS which supports Win32 API (incl. WinE under Linux). Of course, you may find some small incompatibilities beginning with Windows 8 but it is nothing which could stop VFP applications. More serious problem are incompatible components from the 3rd party vendors.

Author Closing Comment

ID: 39898579
As you suspected, I was using MS Office Excel 64 bit. Once I installed the 32 bit version, my application again works as expected.

Thank you very much for your help!

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In this blog post, we’ll look at how using thread_statistics can cause high memory usage.
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
Hi, this video explains a free download that you can incorporate into your Access databases, or use stand-alone for contact management. Contacts -- Names, Addresses, Phone Numbers, eMail Addresses, Websites, Lists, Projects, Notes, Attachments…

600 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question