We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Speed in Access 2007 Multiple Connections

Medium Priority
452 Views
Last Modified: 2012-05-11
I once created a donor database in Microsoft Access 2003 for a non-profit organization. On problem we had was the speed after 3 users connected to the back end. They were always connected to the back end at all times.

I've recently started using Access 2007, and I am nearly finished with a project for a 300+ employee company to manage their engineering requests. I've never launched a live project with Access 2007, and I'm wondering if this connection issue was because of Access 2003 or if my tables were set up wrong.

My question is, how many concurrent connections can access 2007 handle without it bogging down? Let's say for this purpose that there are always 12 different terminals connected to one back end on a network, will performance suffer as users try to add records? I know there will be *some* performance loss from multiple connections, but not all the users will be entering records all the time. This is how my 2003 database worked also, but for whatever reason, the 2003 project seemed to slow down for everyone regardless if all of the users were actively using the database. It seemed as if just because users were conencted was enough to slow it down.

What should I expect from Access 2007? Anything different? How should I go about setting up the back end portion?

Thank you very much for your help
Comment
Watch Question

Database Architect / Application Developer
CERTIFIED EXPERT
Top Expert 2007
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Thank you mx for your speedy reply,

I have one more related question. On the donor database that was slow, I just placed the back end on a shared drive (Mapped to a directory in Windows) on the network. Should I place the back end elsewhere or is it acceptable to simply place the back end anywhere that is shared on the network?

Thanks again for your help,

Charlie
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Application Developer
CERTIFIED EXPERT
Top Expert 2007
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
Thanks for your help MX. You answered all my questions on this topic. I have another question I'm posting separately. Perhaps you could answer that one as well? I'm new here and noticed your credentials are quite impressive. I'm sure you would be able to help. Thanks again.

Charlie
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Application Developer
CERTIFIED EXPERT
Top Expert 2007

Commented:
I would suggest spending some quality time reading the information contain within the following links, written by long time experts in the Access world. They pretty much cover everything I could possibly say.

100 Tips for Faster Microsoft Access Databases:
http://www.fmsinc.com/MicrosoftAccess/Performance.html

Ken Getz tips from Access 2002 Developer's Handbook:
http://msdn.microsoft.com/en-us/library/aa188211%28office.10%29.aspx 

Improve performance of an Access database
http://office.microsoft.com/en-us/access-help/improve-performance-of-an-access-database-HP005187453.aspx

Microsoft Access Performance FAQ:
http://www.granite.ab.ca/access/performancefaq.htm

mx
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.