Re: Access Security not secure

From: Joan Wild (jwild_at_nospamtyenet.com)
Date: 03/24/04 

Date: Wed, 24 Mar 2004 18:33:27 -0500

The wizard in 2000 does not work. You should secure it manually. Actually
there is no reason that you can't use the 97 version of the mdw with
2000/2002. 

-- 
Joan Wild
Microsoft Access MVP
<anonymous@discussions.microsoft.com> wrote in message
news:12e4001c411f3$debfe6a0$a501280a@phx.gbl...
> It was and is secure in the access97 version.
> In your test with using a new workgroup and running the
> wizard it was in access2000 then again in  access2002
> >-----Original Message-----
> >From your description, I'd say that it wasn't secure in
> 97.
> >
> >In your test with using a new workgroup and running the
> wizard - what
> >version are you doing this in?
> >
> >-- 
> >Joan Wild
> >Microsoft Access MVP
> >
> ><anonymous@discussions.microsoft.com> wrote in message
> >news:12b7801c411c7$a04495f0$a301280a@phx.gbl...
> >> Actually, I am using the workgroup that has been used
> with
> >> access97 for years. However, I have tried creating a new
> >> database importing the structure and data then creating
> a
> >> new workgroup when I secure it with the wizard all seems
> >> to work well until I try to access the database on the
> >> shared drive from a computer with a fresh load of
> >> access2000 or access2002 that has the default workgroup.
> >> At that point, there is no security on the database.
> >> The old workgroup has several groups and hundreds of
> users
> >> so I hesitate to use a new workgroup but I would if I
> did
> >> not continue to get the same results.
> >> >-----Original Message-----
> >> >It is not secured properly.  The first step is to
> create
> >> a new workgroup.
> >> >It sounds as though you are modifying the standard
> >> system.mdw.
> >> >
> >> >Follow every step outlined in the security FAQ:
> >> > http://support.microsoft.com/?id=207793
> >> >
> >> >
> >> >-- 
> >> >Joan Wild
> >> >Microsoft Access MVP
> >> >
> >> ><anonymous@discussions.microsoft.com> wrote in message
> >> >news:fe9401c411ba$c70a3260$a601280a@phx.gbl...
> >> >> I created the Administrator and added him to the
> admin
> >> >> group, removed the default admin user from the admin
> >> >> group, removed all rights that the admin user has on
> the
> >> >> database, removed all the rights from the user group.
> >> >> No luck if I try to open the database from a computer
> >> that
> >> >> is attached to the default workgroup I have full
> access
> >> to
> >> >> the entire database.
> >> >> I tried creating a new admin group (admin1), gave
> admin
> >> >> rights to admin1, and removed admin rights from the
> >> admin
> >> >> group still same results. Security is nonexistent if
> I
> >> >> open the database from a computer with a fresh load
> of
> >> >> access2000 or access2002 that has the default
> workgroup.
> >> >> Any help would be appreciated
> >> >> >-----Original Message-----
> >> >> >Hi,
> >> >> >
> >> >> >First you'll need to create another user(eg.
> >> >> Administrator) and add him to
> >> >> >the admin group.(This is very important or you
> going to
> >> >> lock yourself out of
> >> >> >the db).
> >> >> >
> >> >> >Then you'll need to remove the default admin user
> from
> >> >> the admin group.
> >> >> >
> >> >> >You can then remove all rights that the admin user
> has
> >> on
> >> >> the database.
> >> >> >
> >> >> >Also try removing all the rights from the user
> group.
> >> >> >
> >> >> >Should secure your database enough.
> >> >> >
> >> >> >Regards,
> >> >> >
> >> >> >Martin.
> >> >> >
> >> >> >"Jerry Gaber" <Jerome.D.Gaber@boeing.com> wrote in
> >> message
> >> >> >news:f4f201c41115$c903a060$a601280a@phx.gbl...
> >> >> >> I have a database that was an access97 database it
> >> was
> >> >> >> secure. If a user attempted to open it directly it
> >> >> forced
> >> >> >> a the user to join the workgroup. The database was
> >> >> >> converted to access2000 then access2002 in both
> >> >> instances
> >> >> >> if the user has allready joined the workgroup the
> >> login
> >> >> >> appears and all works as expected. however if the
> >> user
> >> >> has
> >> >> >> not joined the workgrout and is connected to the
> >> default
> >> >> >> workgroup access is granted to the database with
> full
> >> >> >> permissions. How do i secure the database so
> someone
> >> >> that
> >> >> >> has access to the sharred drive cannot access the
> >> >> database
> >> >> >> without joining the correct workgroup?
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Relevant Pages

  • Re: Access Security not secure
    ... The first step is to create a new workgroup. ... > I created the Administrator and added him to the admin ... > No luck if I try to open the database from a computer that> is attached to the default workgroup I have full access to> the entire database. ... >>Should secure your database enough. ...
    (microsoft.public.access.security)
  • Re: Is someone hacking into our database?
    ... is only about 90-100 mb in size) because the database goes screwy and begins ... but that I know of no way to keep it secure (due to the ... I changed to that workgroup, ... is a member of the Admins Group in system.mdw. ...
    (microsoft.public.access.security)
  • Re: Baffled By Security Wizard
    ... I did in fact add the Group to my secure workgroup. ... I'm not clear on why importing the ... objects into a new database was critical. ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... I'd say that it wasn't secure in 97. ... In your test with using a new workgroup and running the wizard - what ... > 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)
  • Re: Able to open secured database with default MDW
    ... Joan and David: I want to thank you both for your efforts to help me. ... The admin user can be in any other group in any other ... system workgroup that does have permission. ... All this and I can still get into the database directly when using ...
    (microsoft.public.access.security)