Posted on 24. Nov, 2010 by in, This has been alluded to in a few places, but I want to get this down so I don’t forget it. Visual FoxPro, a 32-bit application, runs just fine on 64-bit machines. Visual FoxPro cannot use 64-bit ODBC drivers however. Does any one knows where i can get the Visual FoxPro ODBC Drivers for Windows. You can use 32-bit ODBC drivers on 64-bit Windows, but you must set them up in the 32-bit ODBC Administrator. This is not the one that’s going to come up if you go through Control Panel. To invoke it, run C: Windows SysWow64 odbcad32.exe and add your DSNs there. Do not just Start, Run, ODBCAd32.exe, as it will not bring up the right one. The 32-bit drivers for SQL Server come with Windows 7 x64, so you don’t have to download them. I hope this helps future me, and possibly future you. I have spent several days working on connecting a web site hosted in a 2012 server and iis 8.5 to vfp files through the vfp odbc driver and it won’t work. Even with the 32 bit connector. Once you try to make the connection, if fails with the architecture mismatch error. I have read every posting everywhere. Can’t make it work, I have now switched to the Access 2010 redistributable available from Microsoft for free. It works, but there are slight differences especially in blank fields are now Nulls, But this can be dealt with in the web code “where field=” ” worked before, Now I must use “where field is null” Somebody prove me wrong. I ran into the same problem and figured out a workaround. I tried to install the current 6.0 version of the VFPODBC DLL, and the MSI package ran. However, when I checked the drivers in the ODBC in the Admin Tools, it was still at version 1.0 I then went into the command line, unregistered vfpodbc.dll from c: windows system32, and then copied the verision 6.0 vfpodbc.dll (from another machine) into the c: windows system32 directory and registered it with regsvr32. Works fine, and give me a chance to relax. Our applications rely on the ODBC connection, and was starting to swet after not getting to work. Hope that helps MD. We have a bunch of code that doesn't work under VFPOLEDB, but works just fine under VFPODBC so we can't just switch. Plus it's a deployed application, so in order to change code we'd have to put a bunch of remote customers through an app upgrade. When I say it still isn't working, I mean the install process is broke ( the VFPODBC.MSI that works with XP doesn't work on Vista ). So there's no way to reasonably instruct an end customer on how to download and install VFPODBC. Yes, I believe you can manually move and register the DLL yourself. My little disciples:) VFPOLEDB.1 DOES work in vista, and windows 7 both x32 and x64.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2018
Categories |