The age old question of Security

[Mr.Kane]

I have created an Access-based "tool" used by the Project Management
Team on a PeopleSoft CIS implementation.

Anyway the initial approach to security is to have a "Security" table
listing the UserID And Password. On Open of the "Tool" there is a
login form with a drop menu where the "User" selects their name and
inputs their Password and upon authentication is granted access to the
"Tool".

I have added several more fields to the table. Checkboxes listed as
"Read-Only', "Read-Write" and "Full Access".

My goal is to have some code that upon authentication of the User,
Access checks this table for permissions and grants or revokes the
appropriate actions to the various forms within the "Tool".

Any thoughts would be appreiated. I know that this sort of question
has been asked several time over in various iterations and so I
apologize

[Rich P]

Greetings,

Security comes in layers. The database security model is one of the
lower levels of security (closer to the source). I don't like to
surprise users by letting them have the ability to enter data into a
front end application - enter data into textboxes, which on updating
they get a nasty message that they are not authorized to
enter/update/delete data. So I make the front end ReadOnly in addition
to implementing database level security. When users see that they
cannot enter data into a textbox or click on a checkbox they will get
the idea that they don't have the correct permissions on that
application or login without having to bring up an annoying message.

Rich

*** Sent via Developersdex http://www.developersdex.com ***

[paii, Ron]

An Access front-end can be opened to the database window with relative ease,
making any "Security" table visible. It's only value is to control normal
report and form access. If that is all you need, get the user ID from
windows, decide for yourself if a password is needed.

"Mr.Kane" <ka*******@gmail.comwrote in message
news:11**********************@h2g2000hsg.googlegro ups.com...

I have created an Access-based "tool" used by the Project Management
Team on a PeopleSoft CIS implementation.

Anyway the initial approach to security is to have a "Security" table
listing the UserID And Password. On Open of the "Tool" there is a
login form with a drop menu where the "User" selects their name and
inputs their Password and upon authentication is granted access to the
"Tool".

I have added several more fields to the table. Checkboxes listed as
"Read-Only', "Read-Write" and "Full Access".

My goal is to have some code that upon authentication of the User,
Access checks this table for permissions and grants or revokes the
appropriate actions to the various forms within the "Tool".

Any thoughts would be appreiated. I know that this sort of question
has been asked several time over in various iterations and so I
apologize

[ManningFan]

On May 1, 2:16 pm, "paii, Ron" <[e-mail]:

An Access front-end can be opened to the database window with relative ease,
making any "Security" table visible. It's only value is to control normal
report and form access. If that is all you need, get the user ID from
windows, decide for yourself if a password is needed.

Werd. We had a pow-wow today with some end users who want us to
create logging tables that track changes made to any one of 50+ tables
and all this junk. If anyone has that much free time that they can go
sabotage data, their manager should be sniffing that out and cutting
their dead weight off the payroll. Keep it simple, pull their
username off the server and bounce it against a permissions table to
see if they should have access to the form or report.

[Tom van Stiphout]

On 1 May 2007 09:24:56 -0700, "Mr.Kane" <ka*******@gmail.comwrote:

Others have already commented on the wisdom of the Security table and
the U/PW.
Personally I would use the Windows login.

To restrict access to a form, write this in the Form_Open event (NOT
in the button_click or menu event):
Cancel = HasAccess(Me)

The public function HasAccess(frm as Form)
would figure out if the user (obtained from Windows login or
otherwise) has access to this form, most likely by inspecting a table
with permissions.

If Cancel is True, then the form will not be opened, so the user does
not have access.

-Tom.

>I have created an Access-based "tool" used by the Project Management
Team on a PeopleSoft CIS implementation.

Anyway the initial approach to security is to have a "Security" table
listing the UserID And Password. On Open of the "Tool" there is a
login form with a drop menu where the "User" selects their name and
inputs their Password and upon authentication is granted access to the
"Tool".

I have added several more fields to the table. Checkboxes listed as
"Read-Only', "Read-Write" and "Full Access".

My goal is to have some code that upon authentication of the User,
Access checks this table for permissions and grants or revokes the
appropriate actions to the various forms within the "Tool".

Any thoughts would be appreiated. I know that this sort of question
has been asked several time over in various iterations and so I
apologize