29 Comments to “In Visual FoxPro, Using 32-bit ODBC Drivers on 64-bit Windows”

  1. techone

    Jul 28th, 2011

    Will Visual FoxPro 9 work with Win 7?

  2. Chris

    Aug 1st, 2011

    Salty Dog,

    If I could hug your neck I’d do it. Thanks, this helped me a lot. I’m the first one in my group to get a 64bit system, and as we still have a lot of legacy VB6 and VF6 applications and free tables, this of course was much needed – and much appreciated!

    Regards,

    Chris.

  3. Jorge

    Aug 1st, 2011

    Salty Dog,

    Let me join your fan club. Your solution was right on the money!

    Jorge

  4. Eric

    Aug 11th, 2011

    @TechOne, Yes VFP9 works very well with Windows 7, 32 and 64-bit. Glad I could help you all.

  5. Sergio Seijas

    Sep 19th, 2011

    I am from Guatemala in Central America. A very important data base for my company is in visual fox free tables. I just migrated from windows xp to windows 7. So, You saved me a lot of work. God bless you.

  6. Abid

    Mar 5th, 2012

    Saved my day

  7. Fabio Reinert

    Mar 9th, 2012

    After hours looking for a solution, it’s here. Thanks a lot. I finished tests with it and it works, finally. Obrigado (kkk).

  8. Marvin (NL)

    Apr 17th, 2012

    This is incredible! I’ve searched for months trying to find a solution. Thx a million!

  9. Kristof

    May 11th, 2012

    What can I do so my visual foxpro application will use these odbc drivers and not tries to use the 64bit odbc connections

  10. Chris

    May 11th, 2012

    Kristof,

    We have found that we have better reliability if we put the ODBC entries under both User DSN and System DSN. Also, if you are using Fox Pro DBFs as free tables then you have to Configure the Visual FoxPro Database entries as ‘Free Table Directory’, not ‘Visual FoxPro Database’. Best of luck to you.

  11. Mark

    Aug 6th, 2012

    Thanks for this!

  12. stanley

    Aug 29th, 2012

    Can I create a DSNless connection to the 32 bit drivers on a 64 bit system? What is the process?

    Thanks, Stanley

  13. Phil

    Nov 27th, 2012

    I’m trying the steps listed above. When trying to add a User DSN I get the error “you must first install the current version of the visual foxpro odbc driver”. I have already placed vfpodbc.dll into the c:\windows\SysWOW64 directory. Any ideas how to get this working? Thanks.

  14. Eric Selje

    Nov 27th, 2012

    Phil, I’m getting that too on this new machine and I’m not sure why. While the post was about getting 32-bit SQL Server drivers running in VFP, not getting a new DSN to the VFP 32-bit driver, I bet someone can help figure out why what you’re trying to do doesn’t work.

  15. […] In Visual FoxPro, Using 32-bit ODBC Drivers on 64-bit Wi […]

  16. Nick Costanza

    Jul 5th, 2013

    Any idea why my SQL SERVER data is now having data truncated and divided by 1000? It didn’t used to happen with a remote view until I upgraded to Windows 7. I did follow the steps to install the 32 bit ODBC driver.

  17. Eric

    Jul 8th, 2013

    Nick, it sounds like you’ve got the parameter set to only pull 1,000 records at a time. Depending on where your connection string is set (ODBC, or within VFP’s database itself) you can tweak that to pull unlimited records or set it to X records at a time.

  18. Jerry Maze

    Dec 17th, 2013

    Thank you, Thank you, Thank you!
    Solved my problem ASAP.

  19. SUSHIL JHABAK

    Sep 17th, 2014

    WHICH VERSION OF FOX PRO WILL RUN IN WINDOWS 8.1 VERSION WITH 64 BITS?

  20. Eric

    Sep 24th, 2014

    Sushil,

    Any of the 32-bit version of VFP should run fine in Windows 8.1 (not the RT version, but the real Windows version). 16-bit versions (DOS, and pre-3.0) would have to be run in VMs.

    Thanks for writing!

    Eric

  21. leeli

    Oct 12th, 2015

    I try this application

  22. Ron

    Oct 12th, 2015

    We have been using VFP 9 (SP1) on Windows 7 for years. The only issue I have had is there is not an Oracle ODBC driver for Windows 7 that will talk to older Oracle databases (we have a 9i database). No problems with newer versions (we have an 11g database as well)

    VFP also works on Windows 10!!

    Regards

  23. Gary

    Mar 17th, 2016

    Issue within my team….Upgraded server from 2003 to 2012R2. Vendor VFP app pointing to SQL Server database. DO not know all the details but application is no longer working. Again without knowing details I thought immediately 32 bit verse 64 bit. Thoughts? Thanks.

  24. Eric

    Mar 17th, 2016

    If the client app didn’t change it sounds more like a problem with the ODBC connection itself. Did they install the 32-bit SQL Server 2012 drivers on each workstation?

    https://www.microsoft.com/en-us/download/details.aspx?id=36434

  25. Aun

    Oct 25th, 2016

    Thank you.

  26. Jason

    Feb 1st, 2017

    I am trying to connect foxpro to MS Access and when I set up the ODBC under SysWow64, I get the error “The specified DSN contains an architecture mismatch between the Driver and Application”. Thoughts?

  27. Eric Selje

    Feb 1st, 2017

    Hi Jason,

    I just tried it here and it works ok. At first I was wondering if you have the 64-bit version of Access (Microsoft Office), but I’m not sure that’s even a thing. Anyone else seeing this?

    Eric

  28. Jason

    Feb 2nd, 2017

    Eric –

    I am running on a 64 bit operating system with Windows 7 Professional. I had no issues when my PC was 32 bit, however now that I have upgraded, I can no longer connect.

  29. KC

    Feb 8th, 2017

    Hi Eric,

    Been encountering this error “The specified DSN contains an architecture mismatch between the Driver and Application” when trying to connect from Oracle using dblink. Configured already the vfp odbc to SysWow64, and the init, listener and tns. Tried to connect via MS Excel from the host and I can access the tables. What should be the issue?


Leave a Reply

Time limit is exhausted. Please reload CAPTCHA.