Chapter 6. Multiuser Issues
You can deploy Access databases as standalone applications as well as in shared systems. Although working with a shared database provides many benefits in terms of efficiency, issues can crop up with regard to users’ activities getting in the way of each other’s data. This chapter provides a few workarounds for integrating Access in a multiuser environment while ensuring data doesn’t get trampled. “Build a Time-Out Feature” [Hack #57] catches and completes idle record edits, thereby allowing others to make changes. “Test for Duplication” [Hack #55] shows a way to validate data before users duplicate each other’s entries. The chapter also covers a distribution method [Hack #56] that makes it easy to get a split database from your development machine to your clients, with the table links already matching the network.
Test for Duplication
Before you insert multiple entries into master tables in a busy data-entry environment, you’ll need a custom validation process to avoid duplicated data.
Just because a database is deployed on the server doesn’t mean the entire application must be in that server copy. A common approach is to put the data in the server database and distribute the forms to the local client computers, inside another Access file. This is a typical Access version of a client/server application.
Because the client installations are Access databases, using tables in the client databases opens up possibilities. One useful technique ...