Because each user will have their own dedicated 'front-end' Brother Cell Phone List 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. On the other side, you have one data store (the server-side) which is automatically backed up daily (by the Brother Cell Phone List normal server systems) and it maintains data integrity too. You know therefore, should the end-user delete their own 'front-end' interface; not all is lost - You simply give them another 'front-end' to use knowing the 'back-end' database was never at risk.
Each user can change objects (if enabled) or more Brother Cell Phone List commonly, add their own queries and reports to provide local based processing which will not disturb the main hub of the database. Users have also been known to use the likes Brother Cell Phone List of Microsoft Excel to run 'one-off' types of reporting like Pivot Tables by connecting Brother Cell Phone List directly to the 'back-end' database. In larger organisations where it's not unusual to have several departments with different versions of.
Microsoft Access (as far back as Access 97) that having Brother Cell Phone List a 'back-end' database on the server can be in essence an earlier engine format (i.e. Access 97 or Access 2000) where the 'front-end' objects can be based in either Access XP, 2003, 2007 or even 2010! Migration is kept to absolute minimum. There are other benefits to splitting an Brother Cell Phone List Access database but I think the above will be a good start. How you split an Access database is simple enough - you'll find this in the Database Utilities and Database Tools section (depending which version you are using).