Exclusive Access Error with One-User

Question

I have created a database for a client and currently, for some reason, only one person can access the database at a time to enter the data. When two people are in the database both get the error: "Microsoft Access can't save design changes or save to a new database object because another user has the file open. To save your design changes or to save to a new object you must have exclusive access to the file."

In my limited experience this error pops up when two users are in the database and one user is trying to modify in design mode. This is not the case in this instance. Nobody is modifying in design mode.

I have not split the database but I am aware that this will probably patch the issue and prevent the error from appearing.

My question is more why is this happening in the first place?

Like I mentioned I'm a pretty inexperienced user - I patched this database together from a previously existing one which did not have this error. I only used the wizards to create and modify since I don't know VBA or any other code.

Let me know if any additional details are needed from me to help the experts out there to solve the problem.

Thanks,

Sidney

Answer 1

Nobody is modifying in design mode. 

My question is more why is this happening in the first place?

The message does not mean that anyone is opening a object in Design mode. it means that the design of an object has been changed, whether in Design mode or programatically. As John suggested, it is most likely that a filter or sort order has been changed which is part of the object's design. Once that has been done, the app is placed in a read only state.

As noted the solution is to split and give each user their own front end. So such things can be applied independently.

Answer 2

Well...

Split the database. Split the database NOW.

This used to be an optional performance enhancement. With each version of Access that's been released in the past several years, it's becoming more and more essential. An unsplit database is an open invitation to wretched performance, lockups, user contention and irreversible permanent corruption.

My guess is that there'[s some macro or code in your startup form that's changing some property (such as the Order By or Filter of the form), but it's hardly worth digging for it; splitting the database will cure this problem and will prevent much worse problems. And splitting is easy and routine.