Exclusive access to the database

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

Guest

Hello all,

My company has three Access database files that were originally created in
Access 97 and was recently converted to Access 2003 (We replaced all of our
old workstations with new ones that came preloaded with Office Pro 2k3). The
problem we're encountering is most accurately described in KB 839782, "You
receive a '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.' error
message when you try to open database objects in Access."

EXCEPT - The error message does NOT occur when there's only one user in a
database; there already IS only one .ldb file in each folder; and changing
the folder(s) did not help.

This is becoming an issue because the managers are frequently modifying
reports while us peons are entering data into the tables. And yes, the data
and the structures are both in the same .mdb file. Don't ask. Anyway, this
was never an issue with 97, but now it's a problem.

Anyone have any idea how to fix this? Is this by any chance connected to
the mysterious (to me) .mdw file(s)? And how do we preserve access (no pun
intended) to all three databases in this fashion?

Thanks in advance,

-Bruce D.
 
With versions of Access after 97, you cannot modify objects while they are
being used. You should split your database into Front-End and BAck-End.
 
Rick -

Do you mean that two managers can't modify the same report at the same time
(which sounds reasonable), or that no one can modify a report that is based
on data being edited at that time?

Thanks again,

-Bruce D
 
I believe it is just the first. I don't have any shared front-ends to test
this for you.
 
Having several people change the same reports (or other program
objects) at the same time, sounds like a recipe for frustration, to me.

Why do they need to? Are you sure this doesn't indicate the lack of
data-enterable report criteria? People shouldn't be changing report
designs, just to select different data. They should be entering data
into selection fields provided by the software, for that purpose.

HTH,
TC
 
Bruce D said:
Rick -

Do you mean that two managers can't modify the same report at the same
time
(which sounds reasonable), or that no one can modify a report that is
based
on data being edited at that time?
Click to expand...


Worse, it means that no one can modify any object in the mdb if someone
else has it open.

You must split the mdb. Even then, you will have issues if you want
everyone to see each other's FE modifications.

The option here is to create a core frontend where they make no design
changes. Give each of them a separate frontend to make new reports, etc.
If someone creates something that all must have, you then add it to the core
frontend.

It is an odd situation that they require making design changes to reports.
 
Back
Top