Re: is 'Admin' a kinda of a genius?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 17:52:33 -0400

While you can't delete the Admin user, when you secure a database, you're
supposed to remove the Admin id from the Admins user group. When you do
that, it doesn't matter whether they try to use a different workgroup or
not: they won't be able to get into your application. 

-- 
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"rocco" <rocco@discussions.microsoft.com> wrote in message
news:C56A3947-36F9-458B-9B56-4E1388960C38@microsoft.com...
> Hello,
> I need to have a concept clear. maybe here someione can help me.
> In few messages  posted I have red that it is possible to have a secured
> database accessed from other workgroup via 'admin' user.
> I have red that since 'Admin' can't be deleted it is in any database and
in
> any wrkgrp.
> In this way my secured database can be accessed from others by using a
> different wrkgrp file (different from the one iused to secure my db).
> I'm wondering. If this is true (which maybe surely not since i'm a bit new
> in these security thing), since I'm talking about a SECURED database, if
> others try to access my database using the default 'Admin' user, they
should
> be asked for the password for that user. Or not?
>
> Thanks,
> Rocco

Relevant Pages

  • 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)
  • Re: Problems setting up access security
    ... The Admin user still owns the database object. ... You secured it using the system.mdw, thinking that you were using your secure mdw. ...
    (microsoft.public.access.security)
  • 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 it possible to make a database secure after creating it as unsecure?
    ... someone else copy this secure database into another computer which has ... default workgroup? ... have permission to open this database file. ... removed the default Admin user's permission to open databases in your secure ...
    (microsoft.public.access.formscoding)
  • is Admin a kinda of a genius?
    ... database accessed from other workgroup via 'admin' user. ... In this way my secured database can be accessed from others by using a ... different wrkgrp file. ...
    (microsoft.public.access.security)