Employee Database/Managers and departments
Here are my tables;
I want to make some employees managers and assign multiple departments to them through a form. Within this form I'll need to be able to see ALL assigned departments and also be able to add or delete departments as they are moving targets.
I created a junction table called tblManagers and I added a field in the employee table that is YES or NO for manager's.
What is the best way to manage the manager's table
Thank you for taking the time to report an issue.
What's wrong... Please write below.
How can I make a button that will automatically insert all the email addresses into the "To" field of a new Outlook message
We have 10 managers that on a regular basis are asked to sit in on 5 work sessions with employees. Managers are randomly assigned to give employees feedback based on this observation, with employees getting a max of 5 sets of feedback.
I am wondering if there is a way to automate this process with access. For instance, can I input all of the employees into one table, all managers into another, set a variety of limitations or rules (e.g. no manager gives the same employee feedback more than once) and have access automatically populate a matrix with employees and managers paired up across these sessions
Initially the database will be accessed from 3 computers: 2 used by the managers and 1 used by employees to clock in/out (kiosk type PC).
I've never worked with a access database that is used from multiple locations, or ever split an access database into front/backend file. The reasons I'm looking into it is to improve stability, speed and secure against accidental editing from inexperienced users. I'm less concerned with malicious 'hacking'.
-MDE file: compiled only version of the code. is this file type for security purposes only, or does it lessen the chances of file corruption/ improve speed
-MDW file: what is this and is it necessary? the 3 computers are always logged on, users will eventually login directly with the system, rather than be identified by the windows user.
-The frontends will be different for managers and employees. should these contain forms only, or should they include queries that are specific to the frontend
-lastly, the database has 13 related tables (and this may increase by the time its completed). is it ok to have this in one file or best to have multiple backend files? say one for employees and one for roster.
For example, if you are working with an employee database, you can create a form that matches an employee record. Depending on your company, you may have several different departments that use employee records. Using Access forms, you can create a custom interface for each department. Each department's form, in turn, will present only those fields that employees in that department need to use.
Trainings are organised in training sessions, since a session can contain more than one training (i.e. First Aid, CPR, and Fire extinguisher)
Employees belong to departments.
Certain trainings are required working in a department, that dictates requiered trainings for an employee.
Now I have two queries:
'Query emp trng req' returning employee id and their requiered training id
'Query emp trng done' returning employee id and their completed training id.
Obviously I like to know which of the 'req training id's' are missing in the 'done training id's' per employee id
There can be training id's in the done query, that are not requiered for that employee.
I have the dBase attached, had to strip a lot from it down to <500k
We have 4 managers and 16 foreman. Each month a manager is tasked with calling 4 foreman for progress reports.
I'd like to create a simple program with Access to have the foreman assigned to the managers differently each month. It would have to remember the past 4 months so the same names aren't assigned to the same managers.
It also has to randomly assign the foremen so the managers don't have the same foreman after 4 months (if that makes sense).
This report is then sent to my managers so they can contact the employee(s) or subcontractor to find out if the building is or has been cleaned. So, my problem is that not every building is to be cleaned every day.
Because of this fact, my exceptions report includes buildings that should not have a call-in for that day. This causes my managers to use more of their valuable time researching buildings that should not be on the report.
How can I get these buildings excluded from my report? I created schedule table, but not sure it is setup correctly. Also, had my exceptions query convert the date and time to weekday (d) in a separate column to compare to this schedule.
I don't want the department with the view and select check box permissions to make any other changes to the database and the ability for them toonly view the other reports.