Inputing Data

CancerStick

Registered User.
Local time
Today, 08:47
Joined
Mar 13, 2008
Messages
12
I have a database with several different tables pertaining to Employee Data. I am using certain tables for information on selected employees. Such as, out of 100 employees, 80 of them have a specific certification.

I've built a seperate table for basic employee information, and a seperate table for those that have this certification. Both tables are related by an employee ID.

What I want to do is place a command button that asks if an employee has a this certification. Yes/ No. If answer is yes, then a modal form pops to fill proper information.

Now, my question is, when I create the relationship as a one to one on the employee Id how do I ensure that the employee Id's match up? Should take off the auto number format on the Employee Id? Do I need to create another VBA code that inputs the employee name into the Certification table off of the Employee Info table?

Am I making any sense?

Hope someone can clear this up for me.
 
Your post sounds as if this is a single type of certification. How involved is the data pertaining to the certification? If this were a situation where there were many types of certifications, with employees having multiple certifications, I could see the use of a separate table, but to be honest, it sounds as if you're needlessly over complicating things here.
 
Your post sounds as if this is a single type of certification. How involved is the data pertaining to the certification? If this were a situation where there were many types of certifications, with employees having multiple certifications, I could see the use of a separate table, but to be honest, it sounds as if you're needlessly over complicating things here.

It is a single type of certification with a license number, issue date, and expiration date. The reason that I have it as a seperate table, is because not all our employees have this cert. In normalization, I understand you're not suppose to have blank fields, so I made a seperate table.
 
CancerStick said:
I understand you're not suppose to have blank fields, so I made a seperate table.
Don't know where you saw that, but that's just plain nonsense! Do yourself a big favor and scrap your second table.
 

Users who are viewing this thread

Back
Top Bottom