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.
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





3 Comments
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?
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
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”