Data Entry Form

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

Guest

I am developing a DB that will keep track of employees' systems access. I
want managers to be able to enter employee's access but I don't want them to
be able to enter employees. I want to be the only one who can enter new
employees because I am always afraid that someone will type over an existing
field because they don't know how Access works.

Anyone have any suggestions of how I could set up this type of situation?
I'm wondering if I would have to enter new employees at the table level only
and then lock all of the fields in that table at the form level. Is that the
only way?

Thanks everyone! :-)
Tanya Lee
 
Just take away the "Insert Data" access to the table for the people who you
don't wish to add a new record. Not sure how this will alleviate the fear
of someone typing over existing data. Seems like you'd only want them to
add records, not update them if that were the case.

User level security allows you to define if someone can add, read, update,
or delete records in a table.
 
If the only reason you don't want users adding employees is fear of
overwriting existing data, then on your employee form you could disable the
name fields and, as Rick suggests, set the Allow Additions property to No.
You could then have a button that the users click to add new employee
records. This could either open a separate form (which has DataEntry set to
Yes) or reset the properties of the existing form to put it into data entry
mode. You could also have another button that would allow editing of existing
records, i.e. the user is making a conscious decision to edit the record by
clicking a button. This should minimize the risk of accidental overwriting,
and means that the responsibilty for maintaining the employee data is back
with the users, rather than the users hassling you every time they need a new
employee adding.

Hope this helps,

Jon.
 
These are great ideas - thank you both!



Jon Ley said:
If the only reason you don't want users adding employees is fear of
overwriting existing data, then on your employee form you could disable the
name fields and, as Rick suggests, set the Allow Additions property to No.
You could then have a button that the users click to add new employee
records. This could either open a separate form (which has DataEntry set to
Yes) or reset the properties of the existing form to put it into data entry
mode. You could also have another button that would allow editing of existing
records, i.e. the user is making a conscious decision to edit the record by
clicking a button. This should minimize the risk of accidental overwriting,
and means that the responsibilty for maintaining the employee data is back
with the users, rather than the users hassling you every time they need a new
employee adding.

Hope this helps,

Jon.
Click to expand...
 
Back
Top