Unmoderated webcam community - Updating a split ms access database
Whether you store the front end on local systems or on a server is an ongoing debate among developers and administrators. Whole books have been written on database security, but it's enough for you to know that you must protect your data. Placing your tables in a backend file protects your database design because users can't directly access the tables via the interface objects in the front end.
Therefore, they can't alter or delete tables, even accidentally.
When you split an Access database file, you end up with two files instead of just one: By linking the two files, users can view and manipulate the data in the backend via the forms and reports in the front end.
This arrangement solves a number of problems inherent to the Access file structure.
In this article, it addresses the pros and cons of splitting the database, and implementing the Database Splitter to create a front and back end database.
Generally, you will split a Microsoft Access application into two databases.
Let’s say that you maintain one database that has 100 local users, and that you update data on a weekly basis.