Why is my database now unaccessible?

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

Guest

I have almost the reverse security problem I usually read about...

I have not done anything to setup security but when I just gave out an
updated version, I was told that "because the systems profiles are locked
down that they can’t access the read-only database.... permissions will not
work with the way our machines are configured. I suggest providing full
access to the database instead of read only."

What surprised me was that I have never setup the MDB file as read only and
never heard of any access problems with it before.

I decided to create a generic new user on my PC, logged in and open the
file.. Although I get a prompt that the file is Read Only, it works fine
after clicking the "OK" button, so that's not the issue...

Having looked in the Tools/Security/Users and Group Permissions, I see that
the group called USERS has full permission (which I expected, although I've
never gone in here to set anything so this must be default)..

1. What would be causing a 'locked down' PC's profile to not be able to
access the MDB?
2. Will removing the Read Only status get this working, if yes, how to do
this?
 
Windows Permissions does not have anything to do with your workgroup file
(mdw).

Your users need to be given full windows permissions if you want them to
open and work on database applications. This is Windows permissions, not
Access. do your users have full access to the folder in which your file
lives?
 
thanks for the quick reply..

I will have to find out about the users access to the file location.
 
just to clarify...

The user only has a single input box to enter a string and will then get
back info from the database..

So does a user need "Full Windows permission" to only perform a query
retrieving data (and not writing/editing/updating a DB) ?

I'm just not clear about this windows permission and if that varies by the
work one will perform on a DB...
 
All users need create/delete permissions on the folder in order for the
associated ldb file to get created/deleted. If they don't have those
permissions, then the first person in will not be able to create the ldb.
The mdb will open as exclusive in that case, and no one else will be able to
do anything.
 
Back
Top