But suddenly you deploy and implement the Brother Cell Phone List Access database into the 'live' environment only to your horror discover that end-users start to complain why it's slow, why it keeps crashing or why the function failed to respond at all. What changed from within the comfort of the developer's safe haven to the vulnerability of the Brother Cell Phone List 'unsophisticated' user? - You can be sure end-users will find a way to break your system! Of course, there many reasons why any of the above happens but performance is a very important factor when dealing with multiple users working with your application.
When you have concurrent users accessing your Brother Cell Phone List database, you need to ideally split an Access database and the following 5 reasons may help to explain why: Performance can be improved keeping the Access database optimised as much as possible. By having one Access database file holding only the Tables stored on a server with another database file holding all the other objects (Queries, Forms, Reports and Macros) stored on Brother Cell Phone List each workstation with a link to.
The server database, you start to split 'processor' processing Brother Cell Phone List time between client and server trying to keep network traffic to a minimum and only call data when you really need to will help improve the performance. Because each user will have Brother Cell Phone List their own dedicated 'front-end' system, you can provide different front-end interfaces for certain users allowing access to a collection of selective objects which is a way to control workflows and security.