multi user security - editting tables through forms

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

SirPoonga - 20 Dec 2004 20:02 GMT

I have a FE and BE for a database. I just want users to use a form in
the FE to add/update data in tables in the BE. How do I set up the
permissions so a user can not modify the data through the linked
tables, only through a form (that uses sql commands to update and
insert).

I want to assume the user know how to un hide a table in the
Tools/Options menu.

Also, I have found out that if you look at the current user through the
Tools/Security/User and Groups Permissions that all the user machines
say the username is Admin.

Reply to this Message

Larry Linson - 22 Dec 2004 02:22 GMT

> I have a FE and BE for a database. I just
> want users to use a form in the FE to add/
[quoted text clipped - 3 lines]
> only through a form (that uses sql commands
> to update and insert).

Don't give them access to the Database window. Control their navigation
through your application with Forms. Open the first of the Forms at startup
(On the database window menu, Tools | Startup.) In a secured database, it is
often useful not to give users permission on Tables, just on Queries against
those Tables (the ones used for RecordSource for your Forms and Reports), as
well.

> I want to assume the user know how
> to un hide a table in the Tools/Options menu.

> Also, I have found out that if you look at the
> current user through the Tools/Security/User
> and Groups Permissions that all the user machines
> say the username is Admin.

Until you define users and the users log in with the name you assign, they
will, by default, be logged in as "Admin".

You can read the Security FAQ for Access 2000 at
http://support.microsoft.com/support/access/content/secfaq.asp and find a
download link at
http://support.microsoft.com/default.aspx?scid=kb;en-us;207793. The details
of security have not changed to warrant updating that paper, since Access
2000.

Read the FAQ carefully, read it again, and then study until it "makes
sense" -- it is not trivial, nor simple. And, PLEASE, do your initial work
in securing your database on a COPY. If you miss a step or make a mistake in
what you need to do, it is easy to make the database so _insecure_ that
anyone can get into it, or so _secure_ that even you cannot get into it.

Larry Linson
Microsoft Access MVP

Reply to this Message