Re: Multiuser Interface on shared servicer with SQL Backend

The only way I can see these particular errors happening is if somehow
users are sharing the same front-end.

Make absolutely sure that each user is the ONLY one using that
front-end, and that they have only ONE intance of it open on their pc.
I agree with Tony that this doesn't look like a SQL Server issue at

On Fri, 5 Sep 2008 05:09:01 -0700, JR_06062005
<JR06062005@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I'm still getting the error messages. The less serious one is below:

The database has been placed in a state by user 'Admin' on machine [computer
name] that prevents it from being opened or locked.

Usually after a few minutes, the users who get this message can try again
and get in. Most of the 55 or so users have gotten this message at one time
or another. It's aggravating, but not catastrophic. The second error
message only affects 3 or 4 of the users, but is catastrophic in that they
cannot get into the database at all. In fact it puts the user in an endless
loop. The user is presented an OK button. Clicking this button only makes
the message reappear. The only way for the user to get out of this loop is
to use the Microsoft Windows Task Manager. The error message is below:

You do not have exclusive access to the database at this time. If you
proceed, you may not be able to save them later.

When attempting to open a database object in Design view, you may encounter
this error message. This occurs because Access requires an exclusive to the
database for some object types since other users may attemp to use the
objects. If you change the name of a table , or its definition of the fields
while someone has the table open, this will result in a serious error for the
user. Therefore, you must acquire sole access to the database while you
attempt to update the object. When you release control of the object, other
users will be allowed to use the database (release your exclusive lock).

"Tony Toews [MVP]" wrote:

JR_06062005 <JR06062005@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

What I had been doing was letting the users link to single front end on a
server. I tried what you suggestesd and actually gave some users a copy of
the FE to put on their desktop. The same error occurred. I am thinking that
the problem may be with the way the data is setup on the SQL server rather
than Access?

This sounds much more like an Access problem on the FE rather than a
SQL Server problem.

Giving *all* users their own copy of the FE MDB/MDE is the highly
recommended practice. If only some users then you're no better off.

Now if you get this message again double check that there is no LDB
file present in the same folder as the FE MDB/MDE with the same name.
This would then mean that someone snuck into the server and is sharing
the MDB/MDE.

If you still get this message then please post back. Also what is the
exact message?

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
Tony's Microsoft Access Blog -

Armen Stein
Microsoft Access MVP