Solved

MS Access 2010 Form Building

Posted on 2016-11-18
3
55 Views
Last Modified: 2016-11-18
Hello,

The end goal is to hook Tableau up to the database and start reporting head count stats. Eventually,

Stats such as;
  • How many FT vs PT employees.
  • How many employees
  • FTE
  • By Department
  • by Group

also trend because I'm adding a hire date and a term date....

So here is the help needed......

  1. I need a form that can be used for "Employee Entry" where 3 pieces of data will be entered. (Short Name, Last and First)
  1. I need a form that can be sued to take the employee that is entered and attach the department, group, hire date etc.... to it. This table is set up called Employee_Reporting
  1. How do I incorporate a "changed" date into this. Because there have been times enployees go from FT to PT or vis versa?

Greatly Appreciated

Michael
-Employee-Reporting.accdb
0
Comment
Question by:Newbi22
3 Comments
 
LVL 36

Expert Comment

by:PatHartman
ID: 41893407
The experts here give advice and answer questions.  If you want someone to actually build the app for you, the best option is to use Gigs or to directly contact one of the experts who is available for contract work.
0
 
LVL 84

Accepted Solution

by:
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 500 total points
ID: 41893417
You should not store the Employee Information in the Employee_Reporting table. Instead, store the ID value from Employee in a field and "relate" that table to the Employee table.

Your Employee table should contain data like HireDate. If your Employee can belong to ONE and ONLY ONE Group or Department then you could also store that in the Employee table. If they can belong to one or more Group or Department then you'll need a Join table that "joins" the Employee table with the Group table, and the Employee table with the Department table.

After fixing that, you can easily create a form to add/edit Employees. Just create a form based on the Employee table and let Access do the rest.

You could also create a form based on the Employee_Reporting table and embed that in your Employee form as a Subform. After linking the two you would then be able to add/edit records in the Employee_Reporting table for each Employee.

How do I incorporate a "changed" date into this. Because there have been times enployees go from FT to PT or vis versa?
You'd need some sort of "EmploymentHistory" table, where you'd store the following:

Employee
HireDate
Status
FireDate

So each time an employee is hired you would enter a record, with the status. When the employee changes status, you would "fire" that employee and "hire" the new one, at the correct status. You could of course change the names if you prefer something different.
0
 

Author Closing Comment

by:Newbi22
ID: 41893450
Thanks for the assistance and direction.
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction The Visual Basic for Applications (VBA) language is at the heart of every application that you write. It is your key to taking Access beyond the world of wizards into a world where anything is possible. This article introduces you to…
I see at least one EE question a week that pertains to using temporary tables in MS Access.  But surprisingly, I was unable to find a single article devoted solely to this topic. I don’t intend to describe all of the uses of temporary tables in t…
Familiarize people with the process of utilizing SQL Server stored procedures from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Micr…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question