forms/subforms

sunshine076

Registered User.
Local time
Yesterday, 20:08
Joined
Apr 6, 2009
Messages
160
I created a form with a subform. However, when I enter in a date it shows up on all the same sheets.
Example I have a relationship to Job Title where it has a bunch on descriptions and then entry dates. Several of us have the same Job Title. The date is duplicated onto each of us who is under a particular job title. Is there any way of manually taking this function off so that each individual under this job has his or her own date instead of everyone having the same?

for the job tables the JobID is the name such as MIL and Title is the description right? For each Job title I have between 10-22 description names that each individual is to be qualified under.
 
Last edited:
Welcome to the forum!

I assume your form/subform are bound to underlying tables. What does the structures to those tables look like (fieldnames & datatypes)? How are the underlying tables related to each other?
 
Table 1=
First Name, Last Name, Job Title = Text
Act Date, Term Date = Date
check box for Union and Active
Clock Number = Number

Table 2 =
Clock ID = Number
Job Title = Text
Descr = Memo
Basic, Proficient, Master = Dates

I have a relationship between the Clock ID and Clock Number and one for Job Title for both tables.
 
If the clockID unique identifies the person, you do not need the job title in the detail table; also it is generally recommended to not have special characters or spaces in your table and field names.

What are you doing with these date fields? Basic, Proficient, Master = Dates
Are you trying to track a person's progress for their stated job title? If so, these dates should be separate records in a related table.

Can you explain in more detail what you are trying to accomplish with your database? That should enable us to help you out a little better.
 
The Basic, Proficient, and Master Dates and dates that the individual is quaified. This database is setup to allow the adiministrator to edit data that is stored for each employee such as qualifications, school and any other information needed. However, I just found out that I am running Access 2000 and I think that is part of my problem.
 
As Bob points out, your problems may be due more to your table design rather than the version of Access you are using. If you are tracking the proficiency progress of a person relative to a specific job title then you need to revise your table structure to something more like this


First a table to hold the information about the people

tblPeople
-pkClockID primary key, autonumber
-FName
-LName

A table to hold all possible job titles

tblJobTitles
-pkJobTitleID
-txtJobTitle

Since a person can hold many jobs throughout their time at an employer, you need to have a one-to-many relationship

tblPeopleJobs
-pkPeopleJobID primary key, autonumber
-fkClockID foreign key to tblPeople
-fkJobTitleID foreign key to tblJobTitles
-dteEffective (effective date for the person in this job, i.e. their start date for a particular job)

Now to track a person's progress in a job:

tblPeopleJobProgress
-pkPeopleJobProgID primary key, autonumber
-fkPeopleJobID foreign key to tblPeopleJobs
-fkAchieveID foreign key to tblAchievement
-dteAchieve

tblAchievements (three records basic, proficient, master)
-pkAchieveID primary key, autonumber
-txtAchievement

You would also have similar tables to hold qualifications, education etc. relative to each person.

Hopefully this will help get you started with a good, normalized table design which is the most critical thing in any relational database. Please feel free to post back with any questions.
 
So what I am doing is having too much info in the tables. Since you are using programming language I will have to convert the database into vb then.
 
So what I am doing is having too much info in the tables. Since you are using programming language I will have to convert the database into vb then.

That makes no sense whatsoever. It has nothing to do with VB and it isn't a matter of having too much info in the tables. It is having the tables designed CORRECTLY for a Relational Database Management System (RDBMS).
 
for my qualifications table it would be something like this:
tbleQual
-pkQualID
-QualTitle
-QualDate

I do have one other question for the jobtable. Since I have several job descriptions under one Job Title once I setup the form it should show all these plus all me join this table with the Achievement table since this where my dates are held correct?
Also with the Job Table I would have it setup where Job Title is the Name of the department the individual is in for example MILL and the Title is the description. Reason why I ask is that there is anywhere's between 10-22 different descriptions for each job.
 
Last edited:
At this point, it sounds like your table structure really needs to be worked on. I would not worry about forms at this point; in fact, I think you should delete all your forms because they will probably not be valid once the revised table structure is in place. To be of assistance to you in setting up your table structure correctly, we really need you to explain in detail what you are trying to capture with your database.


With respect to your qualifications table below:

tbleQual
-pkQualID
-QualTitle
-QualDate

Do the the qualificatons relate to a job or an individual?


I am really confused by this statement:

Also with the Job Table I would have it setup where Job Title is the Name of the department the individual is in for example MILL and the Title is the description. Reason why I ask is that there is anywhere's between 10-22 different descriptions for each job.


In a typical organization there can be many jobs within a department. Are you saying that a department in your organization has only 1 job? With respect to the 10-22 different descriptions, are these really skills that pertain to a job? And is it these skills that you are rating your employees on as to being basic, proficient or master?
 
What this database is is going to be a huge training matrix that will allow the administrator to keep track of all employees in regards to departmental training, hiring date, termination date, qualifications such as SQR, DSQR and the date of attendance and when next one is due, eye exams, stamps (if applicable), knowing who is in what department,

As for my statment above each job as its own job description for example
Admin must be trainined in muli phone usage, know customer relations, type 50 wpm, etc.
Each of our deparments have different descriptions each one is not the same.

Each individual is rated by Basic, proficient, and master for training and these are the dates that will be entered into the database.

I have attached what I have done so far. However, for the achievements I don't really know what that is for. I know that it should be the departmental training and then I need one for other training because each employee is required to have different qualifications. The JobDesc is going to be a list of all the required departmental training that should go with the achievements (i.e. Basic, Proficient, Master).
I hope this somewhat helps
 

Attachments

Last edited:
To be honest, it is not detailed enough, but let me try to sketch out something & ask more detailed questions.

You have employees; each employee has a job title and is assigned to a department. Tied to the job title are several skills that the employee will be evaluated against and that information will their skill level will be recorded (basic, proficient, master). I also assume that their skill level can change with time on the job, training or a combination thereof.

I must also assume that an employee can change from one job title to another as well as from one department to another and in so doing, the qualifications, training etc. will change.

Can a job title be found in multiple departments? For example, do you have an admin in the Quality department and an admin in the Accounting dept? Are the skills required for the admin in each of these departments the same or different?

Are qualifications obtained as a result of successfully completing a training class? In other words, are qualifications tied to training or are they independent?

I don't know what SQR, DSQR (quality related acronyms) or stamps refer to; could you explain further?

Eye exams seem like something outside of either training or qualifications. What bearing do they have on doing the job?
 
For each job Title they cannot be in each department however some of the job descriptions can be. Our company is divided up into several groups such as
Quality - Engineering - Production - Purchasing - Management under each of these are a listing of job titles the only one that share a job title is our Qty / Eng Asst. Otherwise the rest of the job titles go under their own name. Some of the employees are cross trainied into different departments such as BURR/MILL.

Each skill is different with the exception of basic qualifications with this each employee is required to know the basic information on our company and that does not change but within each job description there are other requirements that are different from other jobs.

The qualification (basic, proficient and master) are tied into the job title/description this will let the user know who needs to be checked for a requal if needed or if more training is needed. The qualification is obtained as a result of completing the independent training each employee is trained at different times.

I will also be adding some additional training that does not pertain to the department but rather what our company is required to do such as Firefighting, Lockout/tag out, MSDS-Right to Know and several other topics. These also will need a date of completion all employees are required to do this type of training.


We have inspectors who are certified as SQR, DSQR by outside companies they go to school throughout the years and here is where I am wanting to create a date completed and date expired and have it pop up when the date is approaching within a certain time frame..

We also have certain inspectors who use a stamp that is assigned to them on our data sheets. This will allows us to know who the inspector was based on their stamp number just in case we need to talk with them.

Some of our Inspectors work on certain parts and the requirements for most outside vendors are eye certification. We need to have these inspectors to have eye exams each year to make our vendors happy. This is another one where I will create a date completed / date expire and have it pop up when the date is approaching or print it out.

Does this clarify some of what I am doing?
 
Last edited:
You say that your company is divided into groups and within each group are job titles. You also mention departments. Are departments equivalent to a group or a job title? Based on this statement
Some of the employees are cross trainied into different departments such as BURR/MILL.

It sounds like a department is equivalent to a job title. Is that correct?


Assuming that I am correct, let's start laying out the table structure starting with this statement:

For each job Title they cannot be in each department however some of the job descriptions can be. Our company is divided up into several groups such as
Quality - Engineering - Production - Purchasing - Management under each of these are a listing of job titles the only one that share a job title is our Qty / Eng Asst. Otherwise the rest of the job titles go under their own name.



tblGroups
-pkGroupID primary key, autonumber
-txtGroupName

tblJobTitles
-pkJobTitleID primary key, autonumber
-txtJobTitle

Since you have at least 1 title that is shared, you have to use the following structure to link the titles for each group:

tblGroupJobTitles
-pkGrpJobTitleID primary key, autonumber
-fkGroupID foreign key to tblGroups
-fkJobTitleID foreign key to tblJobTitles


A table to hold the basic employee information
tblEmployees
-pkEmpID primary key, autonumber
-txtFName
-txtLName

Since an employee can be trained in multiple jobs titles, you have to capture that using this structure

tblEmpJobs
-pkEmpJobsID primary key, autonumber
-fkEmpID foreign key to tblEmployees
-fkGrpJobTitleID foreign key to tblGroupJobTitles

Now let's work with this statement:
Each skill is different with the exception of basic qualifications with this each employee is required to know the basic information on our company and that does not change but within each job description there are other requirements that are different from other jobs.

You need a table to hold all of the possible qualifications no matter what job they are for.

tblQualifications
-pkQualID primary key, autonumber
-txtQualDesc

Now since you have basic qualifications that are common to all jobs you have to tie those as well as the specific ones to each job

tblJobQuals
-pkJobQualsID primary key, autonumber
-fkGrpJobTitleID foreign key to tblGroupJobTitles
-fkQualID foreign key to tblQualifications

Now you have to link the employees achievement with each of the respective qualifications for their job

tblEmpJobQual
-pkEmpJobQualID primary key, autonumber
-fkEmpJobsID foreign key to tblEmpJobs
-fkJobQualsID foreign key to tblJobQuals

Since an employee can be assigned various ratings (basic, proficient, master) for each qualification over time, you have a one-to-many relationship

tblEmpQualEval
-pkEmpQualEvalID primary key, autonumber
-fkEmpJobQualID foreign key to tbEmpJobQual
-dteEval (evaluation date)
-fkEvalID foreign key to tblEvaluation

tblEvaluation (holds 3 records basic, proficient, master)
-pkEvalID primary key, autonumber
-txtEvalDesc

Now with regard to training, I'm not sure how to do this exactly, but I'm guessing that you need a table to hold all possible training courses

tblTraining
-pkTrainingID primary key,autonumber
-txtTrainingCourseName
-longFreq

You might include a frequency for those training courses that need to be taken on a regular basis. You can then use that to calculate the next time an employee needs to take the course

It sounds like certain types of training are associated with job titles, so you would join those similar to how I joined job titles with qualifications. And then you would link each required training to the employee. You would capture the date of the training for that employee assuming that an employee may undergo the training several times during their time in your employment.

You would include the stamp # in the table where you join the employee & the job. You would leave the field blank for those employees that do not have a stamp #

Hopefully this will be enough to get you started.
 
Thanks so when I get to the step of creating the actual form how will I know what jobdesc goes with each job title since it is all together in one file without a title next to it to help place it in the right location.
 
You still need to refine and finalize your table structure before you move on to your forms. You will need several forms and on those forms you will have subforms. You will also need some combo boxes. To break it down somewhat, the table on the one side of a one-to-many relationship would be bound to the main form while the table on the many side of the relationship would be shown as a subform on that main form. Perhaps this site that gives some Access tutorials can better help you out. The person responsible for the tutorials is a well respected Access developer on several forums.
 
I am going to work on this through the weekend. If I have any more questions I will ask next week. Thank you for your help.
 
I do have one additional question while I am working on the tables themselves I noticed that the QualDesc isn't linked to the Job Title why is this done that way? I have only 9 group names and 35 Job Titles while several of these job titles fall under the groupTitles.
Couldn't I create a new table and call it Jobs and have a
pkJobID,
fkJobTitleID to JobTitles
QualID foreign key to EmplJobQual

I think this would answer my question. What do you think?
 

Users who are viewing this thread

Back
Top Bottom