General Question

  • Thread starter Thread starter Devin Spilker
  • Start date Start date
D

Devin Spilker

I have developed a database for many people to share. I put the DB into a
shared file that all can access without difficulty. Everything works great
with the exception of one small thing. When one person has the database
open, another cannot open it until it is closed. This is a big problem as
many of us need to have it open at the same time. In order to try correct
this problem I basically made the database as unsecure I could with hopes
that the above would not happen. Unfortunately, it still is and it is very
frustrating. I am utilizing MS Access 2000. Any ideas as to how I can
correct this issue. Thank you very much for your help!

Devin
 
First, check that every user of the database has full Windows
read/write/delete permission on the folder where the database is. Also
check that the database does not have the "read only" checkbox set in
its Windows file Properties.

Second, you should not have several people updating a single mdb file
simultaneously. This is commonly believed to increase the chance of
data corruption. You should split the database into a so-called
"front-end/back-end" structure. Google Access groups on those terms (or
FE/BE, or similar) for more information.

HTH,
TC
 
Eveyone has pemissionto the folder and it is not read only Even when I
split it into a FE and BE popl cannot edit i at the same time (which is
needed). Any suggestions?
 
Have you secured your database with user-level security?

What message are you getting when the second person tries to open it?

Does each person have their own copy of the FE database?

TC
 
I have it split between a FE and BE. When I try to access the database
while it is already opened by another user I get the following error
message: "The database engine could not lock the table 'Downtown' because
it is already in use by another person or process". Everyone has
rights/access and I have no restrictions on the table. I am using a macro
to open up a form when I get this error message. I use a macro for this so
I can make it an "add" only form. Any ideas?

I am not sure where to go from here. Any help is much appreciated
 
It sounds like your form (or some other code within your database) is
trying to lock that table exclusively. Ergo, the second person who
tries to open the form, will get that error.

How do you mean, you are using a macro to make it an add-only form? If
you want a form to be add-only, you just set the AllowEdits and
AllowDeletion properties of the form, to No (or False, or whatever it
is).

HTH,
TC
 
Back
Top