I have FedEx Ship Manager and UPS Worldship on a Windows 7 64-bit machine. Both products use ODBC 32-bit driver. I need SQL Native Client driver to connect to SQL Azure since I have to select default. I've installed Visual FoxPro driver from this link on my 64 Bit Windows 7 Home Premium OS and tried to register vfpoledb.dll using REGSVR32. I could able to register this dll but when run my applic. The driver successfully installed on my Win8.1 64-bit system. Then, using Access 2013 32-bit, I was able to successfully link to the VFP databases used by some old software that I still use. Saved me the headache of trying some of the workarounds I had been coming across on other sites.
I've installed Visual FoxPro driver from this link on my 64 Bit Windows 7 Home Premium OS and tried to register vfpoledb.dll using REGSVR32. I could able to register this dll but when run my application which accesses VFP database is throwing the following error:
System.InvalidOperationException: The 'VFPOLEDB.1' provider is not registered on the local machine.
The same application is working fine in 32 bit Windows 7 Home Premium OS without any issues. I have googled for 64 bit VFP driver and found out that there are no VFP drivers for 64 bit OS from this link. Kindly help me to resolve this issue.
I have found out that there is no 64 bit VFP Driver for 64 bit OS. All we have to do is to change the build option in project properties and set the Platform Target to X86 instead of Any CPU. Build the application for X86. Please refer to this for more details.
This Page describes how to run the 32 bit drivers on 64-bit windows. (You must set them up in the 32-bit ODBC Administrator.)
I just upgraded from windows 7 64 to Windows 10 64. Now I am having problems with the Visual FoxPro driver. I am using the 32-bit ODBC manager (C:WindowsSysWOW64odbcad32.exe). When I try to add or edit a Visual fox pro source I get the following error:
I checked for C:Windowssystem32vfpodbc.dll and it does exist. Why am I getting this error and how do I correct it?
To check :
HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INI
, subkey of yourdriver, if the listed files do exist.C:WindowsSystem32
is inaccessible and is automatically substituted to C:WindowsSysWOW64
.So a path to System32 should be replaced with SysWOW64.The problem could also be an incompatibility with Internet Explorer 11 or Spartan.
Have you been using IE11 when you were still on Windows 7?
If no solution is found, there is always the option of downgrading back to Windows 7.
In case everything else fails, like it just happened to me today, try installing VFP 9 Service Pack 2 Runtime, available at http://www.foxpert.com/download/runtime.html and https://github.com/VFPX/VFPRuntimeInstallers
The reasoning is that this installer includes both VFPOLEB and VFPODBC drivers, and it successfully installed on a Windows 7 machine where all the other standalone installers failed.