Jan. 12, 2011, 5:35 p.m.
posted by osi
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" [Post #57] catches and completes idle record edits, thereby allowing others to make changes. "Test for Duplication" [Post #55] shows a way to validate data before users duplicate each other's entries. The chapter also covers a distribution method [Post #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.