Questar_EP
asked on
Microsoft Access 2007 slow when opening remote files.
We recently upgraded our Denver Office to Office 2007 and since the upgrade the remote databases are running at a crawl. If I copy a database to a local server they seem to work fine but from a server in one of our remote offices it runs way slow. Our connection speed doesnt seem to be an issue as both offices are at 6mb and this problem wasn't there when we had Office 2003. Any Ideas?
ASKER
We have a WAN connection of 6mb on both sides and no VPN is necessary. I did try to use the old 2003 version and also tried a coverted database. Both have the same result.
WAN + Access = trouble. There is on expert here (Databasemx) who apparently successfully runs Access applications over a WAN connection, but this would be the exception and not the rule. In most cases, trying to run an Access application over a WAN is tedious, unreliable, and almost certain to result in corruption.
If you're having the same result with all 3 "versions" of your database then you'd have to assume that the culprit is the common item between the 3 - and that would be the connection.
Here's a write by Albert Kallal regarding why a WAN is not the best choice for Access:
http://members.shaw.ca/albertkallal/Wan/Wans.html
Also, regardless of what your provider claims to provide in terms of speed, unless you've purchased a dedicated line connecting your offices then you're at the mercy of the internet route. As traffic increases your bandwidth decreases, and there's little you can do about it.
To me, your best solution would be to move to Terminal Server, assuming you can afford the cost. The next best would be to move to a server-type database ... this would provide some type of relief, but the only real way to improve speed and reliability is to move to a fully unbound solution with a server database ... this would solve your troubles, but would of course cost in development time/cost.
If you're having the same result with all 3 "versions" of your database then you'd have to assume that the culprit is the common item between the 3 - and that would be the connection.
Here's a write by Albert Kallal regarding why a WAN is not the best choice for Access:
http://members.shaw.ca/albertkallal/Wan/Wans.html
Also, regardless of what your provider claims to provide in terms of speed, unless you've purchased a dedicated line connecting your offices then you're at the mercy of the internet route. As traffic increases your bandwidth decreases, and there's little you can do about it.
To me, your best solution would be to move to Terminal Server, assuming you can afford the cost. The next best would be to move to a server-type database ... this would provide some type of relief, but the only real way to improve speed and reliability is to move to a fully unbound solution with a server database ... this would solve your troubles, but would of course cost in development time/cost.
ASKER
Yes. I do agree with you that we should not be using the WAN this way and I believe that I will try to setup a Citrix connection to the database or something like that. It just seems odd that it worked fine in Office 2003 and now that we upgraded to 2007 it works like this.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Did you convert the databases to use the new ACCDB format, or did you simply open the 2003 databases using Access 2007?