Updating a split ms access database when ex starts dating

Access is a desktop database, and you can store data and interface objects in the same file.But most developers agree that a split database is easier to protect and maintain.Perhaps the biggest incentive for splitting a database is to supply data to multiple users over a network.By storing the backend on the file server and distributing the front end to workstations and users, many users can access and manipulate the data.Most commonly, on a shared network drive or even a shared folder on your own machine (as long as your machine is on when the file is needed by other users! You can back up your Access Data File whenever you need to, and relocate the file if needed.You will need to make sure the front-end database file(s) always know where the Access Data File resides.You'll be able to ask any tech support questions, or chat with the community and help others.One of the important decisions that must be made before a Microsoft Access Database can be distributed is the form that the database will assume after the deployment.

This item is a must to make upgrades to your end users easier.A common question raised by many Access users creating a multi-user database is how best to deliver your solution so that it is secure, fast, and upgradeable.Access database deployment within your organization, or to your end customers, should be well thought out in advance to avoid performance issues, reliability problems, or potentially significant security or data loss issues.The second file is what is usually called your "front end" database.There is really no data stored in the file, it only contains your forms, queries, reports, macros, VB modules, and With your data separated from the user interface (forms/queries/reports) and business logic (VB/macros), you can keep the data anywhere that your users are able to gain access.