I don't want exclusive access

[NISMOJim]

I touched on this question as a side thought in a previous thread, but never got an answer, so here I go again.

When I try to open a particular database, I get a message that says
"You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later."


I can click the "OK" button 5 to 15 times and it will finally open so it can be used, but I cannot edit it without the same message popping up again. This only happens if someone else has the database open, otherwise it opens fine. It is in a trusted zone, and has a default open mode as shared. After looking through the options, everything is set up the same as my other databases, which all open fine if someone else has them open at the same time.
The only difference I can find is that this database has a table that is linked to another database as a source for a combobox in the other database. I deleted the links and tried again, but the problem continues.
How can this be fixed?

[ItsMe]

...This only happens if someone else has the database open, otherwise it opens fine....

It makes sense to get that message if other people are using the database. However, you should only get that message when you are trying to edit the design of the database or one of its objects.

So, if the message is displayed when you open the database, you need to determine why Access believes you are trying to edit the design. There must be some code or a macro running that is causing this. Maybe you can build a temporary, unbound, splash form and have this new form open at startup. Place a single control button on the new splash form to open the form that would typically open at startup. Be sure to use VBA to build the control button and not the wizard.

With that you can study when and where the warning message is displayed.

[NISMOJim]

That's why I come to you guys with stuff like this! Great idea! I made the form with just the command button you described, and it now opens normally at startup to that form when someone else is using the db. The button opens frmMenu, which would normally open at startup. frmMenu then opens normally, without the exclusive access message, which makes me wonder again where the problem could be. I believe this is some progress, but I'm not sure where to look from here. If the problem is with frmMenu, shouldn't I have gotten the message when it opened from the button?

[ItsMe]

I would think so but I have seen similar results before. Not sure I have really ever been able to put my finger on the cause but have been able to get rid of the symptom.

Something is causing the startup process to think that the form is being opened in edit mode or something. Maybe you can look at the form's properties and change some things around. maybe Allow Layout View = No

Is the form bound to a table or query? I would start going through the properties and limiting any property you can that is not needed.

I don't know if it ever does anything, but you could maybe trick Access and save the DB after opening the form in form view. Double click the form object in the nav pane and after it opens, save the DB using the save icon.

[NISMOJim]

I ended up recreating the menu form and copied the code behind each button and now it works fine again. Maybe something on the form itself was corrupt? Not sure, but we're back in business. Thanks again!

[ItsMe]

Thank you for reporting back. I guess a corrupt form is the case. I would like to think there is something more specific causing the problem but, until it gets nailed down....