Go to Top

Issues with Access and Windows 7 64bit

UPDATE: This issue has been solved! Please review this post to learn more.

I’d like to ask all of you to make sure you verify your Access app will work with Windows 7 64 bit before your clients commit to large PC purchases using the OS.

ADVERTISING
ACCESS SAFETY AND TRAINING DATABASE

Access too slow on Windows 7 64 bit
At one point I had two clients, running different apps I designed, who decided to migrate their staff from Windows XP to Windows 7 64bit. Both went from a speedy application to unacceptable performance, one of the clients couldn’t get the program to work anymore!

Nothing changed, all they did was purchase new PCs with Access 2010, or 2007, everything else was the same, same server, network, database, code, etc.

Windows 7 SP1

I’ve read posts from others saying SP1 had damaged their app, my issues had come up prior to SP1 so I don’t think they are related.

We tried EVERYTHING

This has be the most frustrating tech support issue I’ve ever had! I tried everything under the sun to resolve this problem to now avail. We even installed XP mode it seemed to work most of the time but for one of my clients it didn’t work too well under heavy use.

Microsoft Tech Support Lacking

Both clients have submitted tickets to tech support, and it’s been weeks of testing back and forth in between large gaps of no response. Since the clients already had PCs running the application it wasn’t a big deal, but I have to wonder if this was a new roll out to new 64 bit machines if it could have gotten really bad. All of the apps I write are considered mission critical and I hate to think would would have happened if the operations would have come to a standstill.

Resolution: Downgrade

One of my clients could not wait any longer for a solution so they just swapped out the 64bit with the 32bit version of Windows 7. The other client is still trying to make it work with Microsoft. You can see his Technet ticket here.

Disappointed

I make my living helping firms across the US and consider myself an Access Evangelist, but when my livelihood is being threatened in this way it really makes me wonder the commitment at Microsoft towards the professional Access developer’s community.

Have you been experiencing similar issues? Please comment below.

Update 4-14-11: Microsoft is now offering a patch for this issue at http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=983246&kbln=en-us

Update 8-22-11 Hotfix no longer available. The hotfix mentioned in the KB article is no longer available. To see the article please click here: http://support.microsoft.com/kb/983246

About Juan Soto

Juan Soto is a Senior Access Developer at IT Impact Inc. and a Microsoft Access MVP. He specializes in Access with SQL Server databases. His passion for Access has led him to helping a wide range of businesses in helping them establish a secure, stable and efficient environment with SQL Server. He’s a frequent speaker at Access user groups nationwide and recently spoke at the Orange County SQL Saturday # 73. If you wish to have Juan speak at your next group meeting you can contact him here.

14 Responses to "Issues with Access and Windows 7 64bit"

  • Brian Morris
    October 11, 2017 - 2:08 am Reply

    Dear Mr Soto,

    I have noticed that for my users who have Access2013 32bit, moving from page to page in a report preview is MUCH slower than those who use a copy of the same app file in 2010 32bit.

    Do you have any idea what is the problem? All using Win7 64bit, same data, same everything except Office.

  • Cesar Alvarado Diaz
    March 24, 2015 - 7:43 am Reply

    The solution found for this problem, with grateful assistance from Microsoft Access Support, was to change the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Access Connectivity Engine\Engines\ACE\MaxBufferSize to 50000
    Then run once more the access and then be all faster.

    • René den Ouden
      June 19, 2015 - 3:34 pm Reply

      Hey all, i have the same problem but don’t have the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0 but the 15.0 and the 15.0 doesn’t have the Access Connectivity Engine\Engines\ACE\MaxBufferSize
      Someone knows were to find this maxbuffersize in the 15.0 ??

      Thanks in advance

      • Kepa
        November 17, 2015 - 10:41 pm Reply

        \\HKLM\Software\Microsoft\Office\15.0\ClictToRun\REGISTRY\MACHINE\Softwarre\Microsoft\Office\15.0\Access Conectivity Engine\Engines\ACE

  • Syed Ali
    September 23, 2014 - 9:30 am Reply

    I have ddr2 desktop which has 1 gb ram and 160 harddisk. Now i need to upgrade ram 2 gb, after install another 2gb slot my system is not supporting it restarts automatically several times.

    i hope i will solve my problem through this blog.

    thankz,

  • ahmad DIB
    June 25, 2014 - 12:48 pm Reply

    Hi Mr
    their is a problem with me, when i run an Access query under windows7 it is very slow but when i run the same Access query under windows xp it is run very fast, what is the solution of this problem
    Please help me

  • Kenneth
    December 6, 2013 - 12:45 pm Reply

    Hi Juan

    Thanks for bringing up this issue. I have a few customers running our pos system with MsAccess database. When they upgrade from XP to Win 7 the program would intermittently freeze up or the processing will slow down to an unacceptable level.

    For one affected customer when the database reaches around 30mb in size the problems become serious and he has to start deleting sale records to make the system work again. This is ridiculous because with good old Win XP another customer running a busy grocery outlet can be using a 350mb database quite comfortably.

    One of the affected customers had to downgrade to Win XP to see a return to normal operation.

    My testing on Win 8 with a mere 40mb database also shows a similar drastic slowdown compared to Win XP.

    Anyway has Microsoft resolved this subject problem yet? If not a lot of heavy-duty programs using MsAccess database would become quite unusable, thanks to Microsoft great support!

    Is this a hardware (64bit cpu, motherboard) or software(OS)issue? If we know at least we can go searching for a solution – like downgrading the hardware or OS … not so sure what I am talking actually.

    Juan, do you have any further insight and good advice on how to overcome this problem?

  • Mahmoud Haroun
    October 6, 2013 - 12:24 pm Reply

    I think I found out the reason : “Keyboard Language” property of the field should be set to “System”.

    This is what I tried, and “YES” the speed is just fine!

    Please spread the word, I have been chasing this for almost a “Year”now!

    Good luck

    • Ben Clothier
      October 9, 2013 - 9:03 pm Reply

      Thanks for sharing, Mahmoud!

      • Mahmoud Haroun
        October 10, 2013 - 3:46 am Reply

        You welcome…
        It was a nightmare and all the talk about network protocols and access buffers was just deviating my mid from the main problem which was in fact more simple and straight foward which is simply the keyboard language.

        Actully I found out by luck is that opening a new form with default fields properties did fix the problem so I checked all the properties one by one and found that the only thing that has changed wad the kyboard language which is logically the thing that is mainly interacting with the slow movements between fields. Seems like acces is having big time conflict with regonal settings of Windows7.

        Anyway, I hope this will help someone to get his trust back in ms access as I have been counting on it in my daily work.

    • Shabir
      November 17, 2016 - 3:46 pm Reply

      Thank you

  • Munna Kumar Singh
    February 15, 2012 - 9:57 am Reply

    Still if you are facing the issue, please see blow resolution:
    Root Cause

    ——————————————————————-

    The issue which we were seeing on Win7 VDIs could be due to the Network hardware device connected with the machine. If TCP/IP scaling is not supported by the network device then the performance will be slow.

    Solution

    ——————————————————————-
    Disable auto tuning level of the TCP. Please follow below steps:
    1.Open command Prompt with admin right (Run as Admin)
    2.Type “netsh interface tcp set global autotuninglevel=disabled”
    3.After running above command restart the machine.

    For other information on this command, visit link “http://support.microsoft.com/kb/935400”

  • Brian Watson
    January 31, 2012 - 2:35 pm Reply

    I took a package from my ISP to include MS SQL 2008. I have a large MS Access 2010 database that works at several organisations successfully. However, I need to close deals with big corporates and require the database to be centralised in several various methods. To test it I posted my SQL database to the ISP. Created an ODBC (dsn) file and linked it to MS Access on my desktop – no problem. Opening the tables – no problem. However, as soon as I open the forms it is very, very, very slow. Even my menu that only has four fields (combo boxes) is extremelly slow. But the funny thing is that the tables open quickly. My Asset Register has 80 thousand records and the table opens in less than 4 seconds. But when opening from a form view it takes 3 minutes.

    Can anyone help?

    • Juan Soto
      February 1, 2012 - 1:12 am Reply

      Hi Brian,

      Sorry to hear you have been affected by this issue. My first inclination would be to try Access 2007 and see if that resolves the issue with speed.

      Kind Regards,
      Juan

Leave a Reply

Your email address will not be published. Required fields are marked *

 

Contact Us
[gravityform id="16" title="false" description="false"]