Database placed in a state by user . . prevents it from being open

[Arkansas Lady]

I have observed this problem on three different machines, with three
different applications. I have come to the conclusion that it must be
something about the computer itself. The problem is not related to the
number of users. I have one user who opens that database and if anyone else
tries to open it after that user, they get this error message.

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

It works fine in a shared information with everyone else. Could there be
something about the software set up that allows this one machine to lock out
everyone else?

Anyone who gets on this machine will lock out all the others. I am
convinced that it must be the way that machine is set up.

 

[Arkansas Lady]

Chris, These applications are being used in a fairly large corporation so I
will contact the IT Support group in that area to have them check this out.
I always use a split db. This problem originally occurred about two years
ago and the best work around I had was to copy the front end db for that
user. However, I now have a customer that has rotating shifts that come end
and it makes it more difficult to do this. The easier solution may be to
have IT support check out the service packs for that PC. The server must be
ok because multiple users can be in this and it does not case a problem.

Thank you for your help.

 

[Arkansas Lady]

That is correct. I have one front end for the rest of the group and I make a
copy for the user who was locking everyone else out.
--
Arkansas Lady

You say you solved the problem previously by "copying the front end for that
user." Does that mean everyone else is sharing the front end db file on the
server, instead of opening their own copy of the front end located on their
own PCs?

Chris

Chris, These applications are being used in a fairly large corporation so I
will contact the IT Support group in that area to have them check this out.
I always use a split db. This problem originally occurred about two years
ago and the best work around I had was to copy the front end db for that
user. However, I now have a customer that has rotating shifts that come end
and it makes it more difficult to do this. The easier solution may be to
have IT support check out the service packs for that PC. The server must be
ok because multiple users can be in this and it does not case a problem.

Thank you for your help.

Sounds like the db is open exclusively on that PC. Is the db split? Copy of
front end (forms, queries, modules, macros, and links to tables) on each

[quoted text clipped - 22 lines]

Anyone who gets on this machine will lock out all the others. I am
convinced that it must be the way that machine is set up.

 

[Douglas J. Steele]

Every user should have his/her own copy of the front-end, preferably on
his/her hard drive.

If you're concerned about ensuring that everyone's using the correct version
of the front-end, see the free Auto FE Updater Tony Toews has at
http://www.granite.ab.ca/access/autofe.htm

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

That is correct. I have one front end for the rest of the group and I
make a
copy for the user who was locking everyone else out.
--
Arkansas Lady

You say you solved the problem previously by "copying the front end for
that
user." Does that mean everyone else is sharing the front end db file on
the
server, instead of opening their own copy of the front end located on
their
own PCs?

Chris

Chris, These applications are being used in a fairly large corporation
so I
will contact the IT Support group in that area to have them check this
out.
I always use a split db. This problem originally occurred about two
years
ago and the best work around I had was to copy the front end db for that
user. However, I now have a customer that has rotating shifts that come
end
and it makes it more difficult to do this. The easier solution may be
to
have IT support check out the service packs for that PC. The server
must be
ok because multiple users can be in this and it does not case a problem.

Thank you for your help.
Sounds like the db is open exclusively on that PC. Is the db split?
Copy of
front end (forms, queries, modules, macros, and links to tables) on
each
[quoted text clipped - 22 lines]
Anyone who gets on this machine will lock out all the others. I am
convinced that it must be the way that machine is set up.