Multi-user locks

  • Thread starter Thread starter Melissa
  • Start date Start date
M

Melissa

I work in an office where lots of people use the database
for different things. We have a problem where if one user
has the database open and a report on their screen,
another person cannot open the database. If others
already have the database open, they can still use it
normally, even if another person has a report open.
Does that make any sense?

Any ideas what's going on and how to fix it without
requiring that everyone keep their database open all the
time? (We're trying to make changes, which means that all
must be out to change things.)

Thanks,
Melissa
 
I work in an office where lots of people use the database
for different things. We have a problem where if one user
has the database open and a report on their screen,
another person cannot open the database. If others
already have the database open, they can still use it
normally, even if another person has a report open.
Does that make any sense?

Any ideas what's going on and how to fix it without
requiring that everyone keep their database open all the
time? (We're trying to make changes, which means that all
must be out to change things.)

Thanks,
Melissa
Click to expand...

Use the Database Splitter Wizard (under Tools) to create a separate
"frontend" database containing the reports, forms, queries, etc.,
linked to a "backend" containing only the tables. Put the backend on a
shared server folder, and give everyone their own copy of the
frontend.

A2000 and later does NOT work well with shared *development* - if
you're altering the design of a Form or a Report, especially if it has
VBA code attached, nobody else can alter the design of anything.
Splitting the database lets multiple users share the data in the
tables without their (local) design changes interfering, and also
provides a lot more stability and better performance than everyone
sharing a single unitary database.
 
Yes, I thought of this, but my boss (who basically
decides what to do with the Database), doesn't think it's
a good idea. Not sure why. Do you have any links to
documentation on how this works and why it's better?

Is this the *only* solution?

Thanks,
Melissa
 
Yes, I thought of this, but my boss (who basically
decides what to do with the Database), doesn't think it's
a good idea. Not sure why. Do you have any links to
documentation on how this works and why it's better?
Click to expand...

Several:

http://www.granite.ab.ca/access/splitapp.htm
http://www.mvps.org/access/tencommandments.htm commandment 6
http://support.microsoft.com/?id=304932 (see the notes at the bottom
of the page)
Is this the *only* solution?
Click to expand...

For shared use of a database on a network, pretty much so (other than
chucking it and redoing everything in Visual Basic or a web app).
 
another person cannot open the database. If others
already have the database open, they can still use it
Click to expand...

If they are using a shared network copy of a
workgroup security file, give them each a local copy
instead.

(david)
 
Melissa said:
NOOOOOOOOOOOOOOOOOOO! Gack, that would take FOREVER!
Exactly.

I'll try to convince him...
Click to expand...

Please tell your boss that this is the unanimous opinion of the MVPs
many of whom have five or more years experience with Access, some
right from Access 1.0.

Tony
--
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
http://www.granite.ab.ca/accsmstr.htm
 
If you are using Access User Security, you will have
a security workgroup file, normally with an .MDW extension,
probably shared on the network in the same place as your
mdb.

If not, you will be using the default copy of system.mdw
created when you installed Access, in a folder on your
C: drive.

(david)
 
Back
Top