Re: Adding new users to an Access 2002 DB

Don't run the security wizard.

So the mdb opens when you are using the standard system.mdw.

It sounds like someone didn't secure it properly, however parts of it appear
to be secure.

When you open it, go to Tools, Security, permissions and check to see what
permissions the Users Group has and what permissions the Admin User has.
You can also check who the owner is of all the objects.

Since everyone is opening the mdb while using their standard system.mdw,
they are silently being logged in as the Admin user, and they have whatever
permissions are assigned to Users Group and Admin User.

You might also check in Tools, security, accounts to see if the Admin user
is a member of any other group.


--
Joan Wild
Microsoft Access MVP

fluvannahoo wrote:
i opened the DB and did a CTRL-G "?dbengine.systemdb" and the mdw
being used is in my "documents and settings" folder in the
applications>Microsoft>access. It looks like it is that way for all
the users. If I rename that file, a new one is created when Access is
opened again. If I try to run the security wizard I get an error
message saying that I can't do it "when you are both logged on as the
Admin user...". In fooling with this I have changed my permissions
somehow so that I cannot open certain forms, and it goes on.

Joan Wild wrote:
Then that indicates that the mdb is not secured. Even unsecured
databases use a workgroup file. Out of the box, Access uses
system.mdw, which silently logs you in as Admin. This is usually
located in the windows system folder.

You should be able to rename the existing system.mdw to system1.mdw.
Then try to open the mdb. Access will create a new system.mdw when
it can't find one, and if your mdb is not secure, you'll get in.


--
Joan Wild
Microsoft Access MVP

fluvannahoo wrote:
No user has to logon and there is no shortcut to the MDB and mdw
files as I've read about. The version of Access is 2002 and the
error message refers to the DB in question. I will post the full
message later.
Thanks for your help.

Joan Wild wrote:
Are you sure it's the system.mdw file that is being used with this
database? That mdw file may be the default one that ships with
Access.

Usually one keeps the secure mdw file on the server, and everyone
uses that for the secure mdb (it's easier to manage that way).

It would help if you gave the full message i.e. doesn't have the
necessary permissions ... to WHAT? Also what version of Access?

If the message is referring to the mdb file, then the user would
need open permission on the database object. If it's referring to
a table/query, then they'd need at least read data permission. If
a form/report, then open permission on it.

It is likely (and preferred) that you assign permissions to groups.
Then you need only create a new user and put them in the group,
rather than assigning permissions to users.

From your description though, I'm not convinced this database is
secured at all. Do other users (where it's working), have to login
to the mdb?


--
Joan Wild
Microsoft Access MVP

fluvannahoo wrote:
This has to be simple but I've inherited a DB and am having
trouble getting a new user access to it. I keep getting the
message that she doesn't have the necessary permissions... go see
the administrator. We are using MS SBS 2003 with XP clients and
the DB in question is not split. I have searched and read and
reread various publications courtesy of Google but simoply can't
figure out how to add her.
The security file is system. mdw and it is stored in the documents
and settings folder for the user. When I use the print users
function it lists 3 users "Admin", the name of a person (who left
the company long ago) and the name of a company. Every
workstation I've checked has the same info. I definitely don't
want to screw up security for the other users so I need to figure
out how to get her access.
Any and all help would be appreciated.


.

Relevant Pages

  • RE: security wizard cannot be run
    ... secure mdb while joined to system.mdw. ... database is very secure) ... Open Access (no mdb). ... Once the database opens, the ...
    (microsoft.public.access.security)
  • Re: Adding new users to an Access 2002 DB
    ... Then that indicates that the mdb is not secured. ... Usually one keeps the secure mdw file on the server, ... need open permission on the database object. ... It is likely that you assign permissions to groups. ...
    (microsoft.public.access.security)
  • Re: Front end, Back end, and restrictions on which Forms can open.
    ... If you are able to open it, then the Users Group still has permissions, or ... logging in as a user that will own the backend. ... it is secured but when I double click on the file, it still opens ... And do I need to secure the FE at all if it is an MDE file? ...
    (microsoft.public.access.security)
  • Re: security only works on my PC
    ... likely the default workgroup file is set to the one you created ... no matter what mdb you open). ... Then use a desktop shortcut to launch your secure mdb The ... just opens to the first screen, and then when they try to look at ...
    (microsoft.public.access.security)
  • Re: Front end, Back end, and restrictions on which Forms can open.
    ... back to assing permissions, none of the user levels i created using the ... using the same method and selecting the same security file. ... it is secured but when I double click on the file, it still opens ... And do I need to secure the FE at all if it is an MDE file? ...
    (microsoft.public.access.security)
Loading