Re: Workgroup files and Open/Run in 2002
From: Ronald Dodge (ronald.dodge_at_cfgraphics.com)
Date: 01/20/05
- Next message: Pattyt: "Locking Database"
- Previous message: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- In reply to: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- Next in thread: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- Reply: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 Jan 2005 12:50:36 -0500
Uhm, Rick,
Did you miss something?
The DEFAULT workgroup isn't going to have the Admin user removed from the
Admins group. The secured workgroup file does.
Ownership: I had already taken ownership of all the DB files with my own
superuser account name including the DB file itself by following through the
steps of creating a new DB file with my own user account, and then import
all objects from the OLD DB file to the new one, which then I removed all
permissions from the Users group along with modifying the permissions while
I was in there to other groups.
What we are getting at, how do you prevent the DEFAULT workgroup from
allowing the Admin user getting into the FE DB file, cause remember, when
you have multiple users, they all have the DEFAULT workgroup file BY
DEFAULT, and unless someone goes through the deal of removing such file from
each individual PC and force them to join the secured workgroup, which that
in turn could also cause some other issues too, so there has to be a way to
prevent the admin user of the DEFAULT workgroup without necessarily changing
it in the DEFAULT workgroup and still prevent them from getting into the
secured DB file.
-- Ronald R. Dodge, Jr. Production Statistician Master MOUS 2000 "Rick Brandt" <rickbrandt2@hotmail.com> wrote in message news:35a6fbF4i0kuoU1@individual.net... > Ronald Dodge wrote: > > Sorry for the long delay as I have been working on setting up forms > > in my FE file. Not only that, but pressured to get this done ASAP > > like by the start of next month. > > > >> By the way if you are even able to open your secure database, while > >> joined to the standard system.mdw, then your database isn't secure. > > > > What needs to be done to prevent the Admin user going into the secured > > database in Access 2002? After all, it's a default account, and it > > can't be deleted for that reason. It's in the Users group, which > > that can't be deleted and not only that, but from what I understand, > > the Admin account can't even be taken out of the Users group. All > > users must be in the Users group in order to open the database. > > The default group "Users" must have zero permissions and the default user > "Admin" must be removed from the "Admins" group and must not own anything. > That last thing "Ownership" is what most people screw up when setting up > security because owners have permissions above and beyond those that you see > in the permission settings. > > If everything is done properly the user "Admin" will not be able to open the > file regardless of the workgroup file being used. > > -- > I don't check the Email account attached > to this message. Send instead to... > RBrandt at Hunter dot com > >
- Next message: Pattyt: "Locking Database"
- Previous message: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- In reply to: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- Next in thread: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- Reply: Rick Brandt: "Re: Workgroup files and Open/Run in 2002"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
