I am converting MS Access 2000 to MS Access 2010.The issue i am facing is,the MS Access 2010 is very slow (even freezes) after conversion.
Previous Config: MS Access 2000 on XP with Link Tables to Sql server 2000 sitting on Windows 2000
New Config: MS Access 2010 on Windows 7 with Link Tables to Sql server 2000 sitting on Windows 2000
Access under New Config is painfully slow or sometimes hangs and crashes
Same situation with a Visual Studio Desktop Application,It runs painfully slow on Win7,while it runs great on XP.
Things I have tried :
- Converting the MS Access 2000 by creating a New MS Access 2010 and importing all the objects from 2000 Version
- Refreshing Linked Tables etc
- Changing the MS Office Max Buffer size in Registry to 55000(as suggested in some MS support sites)
Little to no improvement so far.
It is hard to reply because the origin of the problem can be multiple.
Since the two clients has not the same OS configuration, we cannot exclude that the problem comes from a difference of configuration between the two OS.
First you can discern if the connexion is slow because of the PC, Access or your DB :
Test : direct connection
You can try the direct connexion to SQL server using a direct connexion instead of linked tables.
For this, you can create a new Access Project connected to your SQL Server. An Access Project is a type of Access database which directly connect to an SQL Server, without linked table. It uses a native client. You can view tables of your SQL Server database directely in Access, and you can edit them. The extension of an Access Project is not MDB but ADP. Access Projects are hidden in Access 2010 but well supported.
To create an Access Project: go to menu File -> New, then click of the file icon, and then choose “Save as type” : “Microsoft Access Project (*.adp)”.
When the ADP is created, it should ask you to enter the parameter for an existing SQL Server database. Enter your parameters.
Then go to the table panel, and try to browse some table and check if it is slow or fast.
If it is slow => then the problem may comes from your PC or the connexion. You can try with another software for testing the direct connection of you have one that can connect to SQL Server.
If it is fast => then the slowness comes from the ACCDB or the ODBC link.
Also check :