Inspection Database

[Guest]

I have never used Access before. I am trying to put together a database that
has a table of employees and monthly inspections. I have completed that table
for the employees. Now, what I need to do next, is where I get stuck. I will
need to include Monthly inspections for all of my employees. We will be
inspecting their vans. My primary key for the employee table is an employee
id. For the inspection table I have the Inspection ID as the primary key. I
can't figure out how to make the employee ID bring up the other employee
information (such as name and department). I got a CD Rom and did training
that way, and do not have time to take an in person class.
I am wondering if any one has done a similar database? Or could give me some
tips.

Thank you for your time in advance.

 

[SusanV]

Hi Kris,

Do you have a field in the Inspection table for the EmplyeeID? If so, have
you set it up as a foreign key to the Employee ID in the Employee table?

 

[Guest]

Thank you for responding!
I do have the employee ID in the employee and the inspection database. I
have not set up a foreign key.....How do I do that?

Again, Thanks!

 

[SusanV]

Under the Tools Menu, relationships, show the 2 tables (right click > show
table), drag the mouse from that field in your Employee table to the
corresponding field in the Inspection table. For more info about
relationships:
http://www.uic.edu/depts/accc/seminars/access2000-intermed/tables-relationships.html

 

[Guest]

Thank you Susan.
I am reveiwing the website and printed out the handout! I like to have
printed instructions!
Again, Thanks!

 

[SusanV]

Glad to help!

;-D

Thank you Susan.
I am reveiwing the website and printed out the handout! I like to have
printed instructions!
Again, Thanks!

 

[Guest]

I think I have did something wrong when I set up my tables.
My employee master table has: employee id, first name, last name, Dept,
Team, and van #.
My inspection table has Inspection #, employee id, last name, first name,
dept, team lead, van #, month, the different inspection parts (front of van,
tools, inventory ETC) Total, Points Possible and Percentage.

I knwo that I should not have to have all of the employee info int he
inspection table, But if I only have an employee # I will not know who is
who.
I have confused myself, so I know this posting will be confusing.
I want to be able to add and inspection in my table and have all of the
employee information prefill after entering the last name or an employee id.
Desperately seeking help!

 

[John Vinson]

I think I have did something wrong when I set up my tables.
My employee master table has: employee id, first name, last name, Dept,
Team, and van #.
My inspection table has Inspection #, employee id, last name, first name,
dept, team lead, van #, month, the different inspection parts (front of van,
tools, inventory ETC) Total, Points Possible and Percentage.

I knwo that I should not have to have all of the employee info int he
inspection table, But if I only have an employee # I will not know who is
who.
I have confused myself, so I know this posting will be confusing.
I want to be able to add and inspection in my table and have all of the
employee information prefill after entering the last name or an employee id.
Desperately seeking help!

The whole POINT of a relational database is that you store things
ONCE. It's the "Grandmother's Pantry Principle" - "A place - ONE
place! - for everything, everything in its place".

Your Inspection table needs ONLY an EmployeeID, as a link to the
Employees table. If you wish to see employee information on the same
screen or sheet of paper as Inspection information (as of course you
will), you can use a Query joining the two tables; or a Form with a
Subform (the best bet for data entry) with the Form based on Employees
and the subform on Inspections; or simply a Combo Box storing the
EmployeeID and displaying the employee name, or any of the numerous
other tools that Access provides.

If you're expecting to look at the table datasheet and find everything
there... DON'T. Tables are NOT designed for human interaction; they're
for data storage, only.


John W. Vinson[MVP]

 

[Guest]

Thank you! Thank you! Thank you!
I have been working on this for 3 weeks!
Thank you for your support and guidance! : )