Placing Database "in a state"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running a database being used on a network. We're still in the early
stages. Occasionally we get a message that one user has "placed the database
in a state" that prevents anyone else from opening it. She has not
intentionally opened the database exclusively. This time around, she did
accidentally attempt to enter the design view of a form, which she has the
permissions to do, but I was in the database so it warned her that she
couldn't. Any ideas as to what is happening? Right now, we can still walk
around the office and get people to shut down and log back in, but as we add
more users (and more important users) to the system, this will be intolerable.

Thanks.
 
From reading your description it sounds like all of your users are opening the same MDB file on the
server. Is this the case?

If so, this is really dangerous! You need to split the database into a FE/BE where each person will
have their own copy of the FE on their hard drive linked to one copy of the BE residing on the
server. This will eliminate those errors and more importantly, reduce the chances for corruption!

I would read some great information on splitting a database by Tony Toews here:

http://www.granite.ab.ca/access/splitapp/index.htm
 
Thank you. In the short run, you've given me a lot more work to do, but
you've convinced me that it will be well worth it. I appreciate the help.
 
You're welcome.
Yes, it will be more work setting this all up but believe me, the benefits far outweigh the effort.
Imagine how much time it would take to fix a corrupted database. How about the cost of down time,
lost data, professional data recovery service, etc?! Trust me, split the database and your life will
get easier.
 
Back
Top