Table creation

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have implemented security and it's working nicely. I have removed all
permissions from the default users group, removed Admin from the Admins
group, and created my own users group with only read design and read data on
the existing tables. I have completely removed all permissions on <New
table/queries> because I don't want users to be able to create these items.
However, when I log on as a user, I find that I am able to create a table and
I can't restrict permissions on it from my administrator account even if I
change ownership. Why is that?

Thanx to all who can help.

Ripper
 
The permissions on <New table/queries> does not have anything to do with
allowing creation of tables. It is simply what is used as the default when
a new table is created.

Making an MDE file will prevent them from creating new tables (I believe)
but I think they will still be able to create their own queries.

Rick B
 
Kewl,

Thanx,

Rip

Rick B said:
The permissions on <New table/queries> does not have anything to do with
allowing creation of tables. It is simply what is used as the default when
a new table is created.

Making an MDE file will prevent them from creating new tables (I believe)
but I think they will still be able to create their own queries.

Rick B
Click to expand...
 
OK, thanx.

Isn't there a way to make the database window unavailable to certain users?
Or, for that matter, all users except the administrator(not default Admin)?
That way they are limited to moving around the database thru forms and
switchboards, but can't create any new objects?

Rip
 
RipperT said:
OK, thanx.

Isn't there a way to make the database window unavailable to certain
users? Or, for that matter, all users except the administrator(not
default Admin)? That way they are limited to moving around the
database thru forms and switchboards, but can't create any new
objects?
Click to expand...

Sure, this is something you should do anyway.

Backup your database; you can easily lock yourself out playing around with
these features.

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on
startup.
Use the features in Tools, Startup to
set the startup form
set your default menu (the custom one you made)
disable all the checkboxes about allowing built in menus, toolbars,
changes etc.
hide the db window (ensure the custom menu you create does not
include the Windows, Unhide item)
uncheck the allow special keys (this will disable the F11 key, among
others)

If you need to bypass these startup features, you can hold the shift key
down while you open the db. If you feel that your users may use this to
bypass your settings, you can disable the shift key bypass - there's an
example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes to
forms, reports and modules (If you do this, be certain to keep your original
mdb in case you need to make changes).
 
OK, I'll do it that way.
However, under the other scenario, suppose a user does create his own table.
I find that even tho I can go in thru my administrator account and take
ownership of the table, then restrict permissions on it, that user still
retains all permissions on it. Why is that?

Thanx alot, you've been waaaay helpful!

Rip
 
RipperT said:
OK, I'll do it that way.
However, under the other scenario, suppose a user does create his own
table. I find that even tho I can go in thru my administrator account
and take ownership of the table, then restrict permissions on it,
that user still retains all permissions on it. Why is that?
Click to expand...

Check both the permissions of the user, and any groups he belongs to.
 
Back
Top