Security(Mdw currently use)

[Hugoroy]

1-Can someone tell me why sometime the .mdw file that I
use to secure my Access database send the
message "Test.MDW currently in use" and refuse to let any
user enter a database

2-How Can I repair this problem?

3-How can I prevent it to happen again ?

 

[TC]

Well, that's not much information to go on!

Is the database secured?
How are you starting it?
What did you do immediately before tghe message appeared?
Were you the only person using the db then?
Is this a new database? a new problem?
What version of Access?

TC

 

[Hugo]

1-My database is secure

2-I start it with a shortcut

3-The message appered just after I click on the shortcut

4-I'm not the only one to use the database and the .MDW
file is use for more than one database

5-it's not a new database but it's a new problem

6-I work with Access XP

 

[TC]

Hugo

It seems that lots of people have had this problem before - but many of them
got no answrer :-(

Here are some answers that I've culled from Google. I can not vouch for them
personally, but they seem like possible causes, to me. Try them & get back
to us.

HTH,
TC

------

It's been so long since i originally posted this message i'll re-cap my
problem: we have a network install of access. occasionally when people
would try to open access, they would get the message: can't access
system.mdw, file already in use. I figured out the problem. The file
permissions on the system.mdw file were set to everyone Read,
administrators full control. This was wrong. I had to remove the
administrators group from this file and just have everyone with read
access. This was because people in the admin group would open the
system.mdw file for Write access, which would lock other people out from
the file.
and I only had to hit my head against the wall for two weeks...

------

I've seen this type of behavior when the permissions on the directory
containing the mdw file are not set correctly. The ldb file will get
created by the first user to access the mdw. The permissions on the LDB
file will be the same as those for the directory. Users that belong to the
right security groups will get through but others won't. When everyone gets
off the ldw is deleted and the whole process starts again.
This may not be your problem but the situation drove me crazy for a long
time.

------

The system32 folder was set to read only, for ordinary users and of course
guess where MS have put the system.mdw file now.
The problem occured because even though system.mdw was set to full access,
ordinary users could either not create the ldb locking file, or if an admin
had it open (hence overriding file security), could not modify it since it
adopted the readonly default from the parent system32 folder.

 

[Sidney Linkers]

Hi Hugoroy,

All users of your MSAccess database need read,write,create and delete
permission on the network folder.

To test this logon with the users network account, create a new textdocument
in the application folder and once created delete it. If this all works ok
then the user has the needed permissions to work with the secured MSAccess
database.
It is still tricky, but MSAccess needs to create and remove .LDB files. It's
a pitty that Microsoft didn't give the ability to create these files in a
userdefined folder.

P.S. Network security is not the same as MSAccess security. Users still
cannot change the database unless you configured the MSAccess security to
let them do so.

Sid.