Re: Access 97 Security issue Can't make a MDE

From: '69 Camaro (ForwardZERO_SPAM.To.69Camaro_at_Spameater.orgZERO_SPAM)
Date: 12/21/04


Date: Tue, 21 Dec 2004 10:01:14 -0800

Hi, Rick.

> I have a user
> ID I used to initially secure the DB (admin) is the username which ALSO
has
> admin rights.

If the Admin user has the right to open the database (or has any other
permissions), then the database has not been secured. Anyone with a copy of
Access can open your database because their workgroup file gives the Admin
user the right to open the database and the ability to administer every
user-defined object in the database. One cannot delete this user, but one
must remove all permissions assigned to this user in order to secure the
database.

For best results, secure the database while joined to the secure workgroup
and logged in as the owner of the database, and don't remove or reduce the
owner's permissions for anything in the database. Ensure that a
user-created workgroup is used for securing the database, not the default
workgroup that comes with every installation of Access.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

"Rick" <Rick@discussions.microsoft.com> wrote in message
news:F7E48327-7ACD-46D9-9219-454392073970@microsoft.com...
> I am the owner of the database, I was signed in with my own user ID which
I
> use for all other security administration for users of the DB. I have a
user
> ID I used to initially secure the DB (admin) is the username which ALSO
has
> admin rights. I am unable to make the MDE as either user. I will read
the
> info that you provided, thank you!
>
> My problem is likely something else, I just assumed since the error
> indicated I needed these other rights to this table that I should be able
to
> CHANGE them and simply proceed!
>
> "'69 Camaro" wrote:
>
> > Hi, Rick.
> >
> > > admin, the user that was
> > > used to secure the database.
> >
> > If the default Admin user was the owner of the database when it was
secured,
> > then the database is not secure. For the steps needed to secure an
Access
> > database, please read the Security FAQ on the following Web page:
> >
> >
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp
> >
> > > When I try to compile the mdb I get an error "The current user account
> > does
> > > not have permission to make an MDE file from this database".
> >
> > It's best to log in as the owner of the database before creating the MDE
> > file, but a non-owner user with the following permissions can usually
create
> > the MDE file without trouble: Open/run database, open exclusive, modify
> > design or administer for all tables, and read design permissions for all
> > objects.
> >
> > > Several suggestions are listed, the one that applies seems to be "Make
> > sure
> > > that the user account has Modify Design or Administer permissions for
the
> > > MSysModules2 table in the database.
> >
> > The MSysModules2 table is a system table. No user has either of these
> > permissions on any of the system tables. For more information, check
the
> > "Can't make an MDE!" checklist on the following Web page to help you
> > determine if there are any other reasons why you can't create the MDE
> > database:
> >
> > http://www.Access.QBuilt.com/html/conversion.html
> >
> > HTH.
> >
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > will be forwarded to me.)
> >
> >
> > "Rick" <Rick@discussions.microsoft.com> wrote in message
> > news:1EB114C1-9185-451B-894F-CDF04A59D224@microsoft.com...
> > > I am trying to make a MDE of a database. I have both Admin user
rights to
> > > the dayabase as a user AND can sign in simply as admin, the user that
was
> > > used to secure the database.
> > >
> > > When I try to compile the mdb I get an error "The current user account
> > does
> > > not have permission to make an MDE file from this database". To make
an
> > MDE
> > > file do the following:
> > >
> > > Several suggestions are listed, the one that applies seems to be "Make
> > sure
> > > that the user account has Modify Design or Administer permissions for
the
> > > MSysModules2 table in the database.
> > >
> > > This seems to be my problem, I do NOT have Modify Design or Administer
> > > permissions for the table. Not signed in as the Admin user or as
myself
> > with
> > > Admin rights. I am not able to CHANGE these rights. Is there any way
I
> > CAN
> > > change these rights? Or have I somehow "Locked myself out of my own
> > database"?
> > >
> > > Any help will be greatly appreciated!
> >
> >
> >



Relevant Pages

  • Re: User Level Security Malfunction
    ... menu, the Users group has no rights to open the database, and it also ... I first create a blank secured file that I ... Remove Admin from Admins group ... Remove all permissions to "new" objects from Admin ...
    (microsoft.public.access.security)
  • Q: low permission cannot convert from A97 to A2000/2003
    ... A97, but the database is sent out and used by contractors (user permissions) ... The admin user has full privileges. ... The problem we are having is converting the database from A97 to 2000+. ...
    (microsoft.public.access.security)
  • Sorting out security
    ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
    (microsoft.public.access.security)
  • Security Wont work
    ... I have set up a database and created a workgoup file. ... the admins group so admin is only a member of the user ... All permissions for the user group are turned off. ... I see in Snelling's security document that there are two ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)