Help! Allowing users limited capabilities to data input

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

Guest

Hi
Let me start by saying that I have had limited experience with Access - I am working on a project that is attempting to collect actual costs attributed to specific tasks (i.e., man hours per task).

We are on a network - and each person has Access on their computer. The idea is to allow each employee to input his/her time into the database and then use this information for cost projections (at the task level) and possibly payroll reconciliations.

Based on what I've read on other chats, it seems that Access may have the security capabilities we are looking for - I am just wondering if someone can direct me to more specific reading or give me the correct terminology that I can use to describe what we are trying to do.

Basically and ideally, each employee would be able to access only his/her data and not be able to change other employees' inputs. There is no real "confidentiality" issue in terms of employees viewing other employees data - we just want to avoid people changing other people's data input by mistake, etc. A group of people should have access to run the reports, etc. as needed. Is this possible

Any help you can provide is greatly appreciated! Thanks in advance, Ingri
 
Once you implement user-level security, then each user will log onto
Access with a unique name. The CurrentUser() function identifies the
current logged-in user. It can be used as a criterion in your queries
so that only records belonging to the current user are displayed.
Also, you use the CurrentUser() function to "tag" newly-created
records or edited records with the identity of the current user.

User level security also includes the notion of groups, so you will be
able to distinguish various people by the groups they belong to.

These are the tasks you will need to go through. They are not super
difficult, nor are they trivial...
- implement user-level security
- modify your data tables by creating a field that will store the name
of the person who created/modified the record
- build queries that use the new field plus the CurrentUser() function
to return the correct records. There is no built-in "currentGroup"
function, but you can find VBA code to determine whether the current
user belongs to a specific group. Use these queries for your forms
- use the BeforeUpdate() event of your forms to populate the
CurrentUser() into your records.

The definitive information source for user level security is the
Microsoft Security FAQ. I have written my own version. Links to both
are on the site in my signature.

Hi,
Let me start by saying that I have had limited experience with Access - I am working on a project that is attempting to collect actual costs attributed to specific tasks (i.e., man hours per task).

We are on a network - and each person has Access on their computer. The idea is to allow each employee to input his/her time into the database and then use this information for cost projections (at the task level) and possibly payroll reconciliations.

Based on what I've read on other chats, it seems that Access may have the security capabilities we are looking for - I am just wondering if someone can direct me to more specific reading or give me the correct terminology that I can use to describe what we are trying to do.

Basically and ideally, each employee would be able to access only his/her data and not be able to change other employees' inputs. There is no real "confidentiality" issue in terms of employees viewing other employees data - we just want to avoid people changing other people's data input by mistake, etc. A group of people should have access to run the reports, etc. as needed. Is this possible?

Any help you can provide is greatly appreciated! Thanks in advance, Ingrid
Click to expand...


**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Thank you so much for your help - I will include this information with my proposed requirements for this new project. I appreciate your time. Regards


----- Jack MacDonald wrote: ----

Once you implement user-level security, then each user will log ont
Access with a unique name. The CurrentUser() function identifies th
current logged-in user. It can be used as a criterion in your querie
so that only records belonging to the current user are displayed
Also, you use the CurrentUser() function to "tag" newly-create
records or edited records with the identity of the current user

User level security also includes the notion of groups, so you will b
able to distinguish various people by the groups they belong to

These are the tasks you will need to go through. They are not supe
difficult, nor are they trivial...
- implement user-level securit
- modify your data tables by creating a field that will store the nam
of the person who created/modified the recor
- build queries that use the new field plus the CurrentUser() functio
to return the correct records. There is no built-in "currentGroup
function, but you can find VBA code to determine whether the curren
user belongs to a specific group. Use these queries for your form
- use the BeforeUpdate() event of your forms to populate th
CurrentUser() into your records

The definitive information source for user level security is th
Microsoft Security FAQ. I have written my own version. Links to bot
are on the site in my signature

On Sat, 22 May 2004 06:56:03 -0700, ingri
Hi
Let me start by saying that I have had limited experience with Access - I am working on a project that is attempting to collect actual costs attributed to specific tasks (i.e., man hours per task).
Click to expand...


*********************
(e-mail address removed)
remove uppercase letters for true emai
http://www.geocities.com/jacksonmacd/ for info on MS Access securit
 
Back
Top