Unanswered: What are the key design issues in making an Access database a multi-user app.
I have an access 2000 database that is used to record employee activities in a university security office. They enter their activities, which includes date, time, location, activity type, etc. The problem is that several officers need to make their entries to the database at the same time. Although the database in on a server and their are shortcuts to launch the application on each work station, if a person trys to add a record while the application is open on another machine, he or she will get an error message "save action cancelled". My feeling is that the problem is related to the fact that the forms are all bound to tables/queries and I need to use unbound forms.
I imagine that this could be a rather involved problem from a design standpoint. If you know of a book or other resource that deals with this issue that would be very helpful.