Gathering information

  • Thread starter Thread starter kmr
  • Start date Start date
K

kmr

I have an end result in mind, but I just cannot figure out the best way to
get to this result. I have a database on staff and drills performed. One
table has staff first and last names. A second table has the first name (a
relationship linking this table's first name to the first table's first
name), date, station, time to ID, pass/fail, and observer. From the
information I have entered, I want to make a list of all staff who have
failed a drill. I have one column for pass and fail, so how to I create
something so that it pulls only the fails from that column? Do I use a
query, form, or report for this?
 
You suggest not using names as a primary key, and instead using auto numbers
or employee ID. I have a problem with, and maybe it's easy to solve and that
I'm just not thinking of it. So, I have one table with all my staff and an
employee ID and a second table with the employee ID and all the drill
information. When I go to enter new drills, I will either need to have all
employee IDs memorized or I will need to look at the other table to see what
the employee ID is. To me, this is creating more work. The reason I chose
to use first names was so that I don't have to memorize anything, and I just
type everything in without having to think. I have 80 staff, I really can't
try to memorize anything or have to look back each time to see what their ID
number is.
 
KenSheridan via AccessMonster.com said:
Whatever the final output format, start with a query which joins the two
tables on the First Name columns. If the Pass/Fail column is a Boolean
(Yes/No) data type enter False in the criteria row of this column in query
design view; if it’s a text data type with values ‘Pass’ or ‘Fail’ enter Fail
in the criteria row. Having created the query you can base a form and/or
report on it.

However, using the First Name columns as the keys is not a good idea. Names
can be duplicated, so are unsuitable as keys. Give the first table an
autonumber primary key column such as EmployeeID and add a long integer
number (not an autonumber this time) EmployeeID column to the second table as
a foreign key to the second table. The tables can then be related on the
EmployeeID columns and employees with the same name(s) can be accommodated (I
worked with two Maggie Taylors once). The redundant First Name column in the
second table can then be deleted.

Ken Sheridan
Stafford, England


--
Message posted via AccessMonster.com


.
Click to expand...
 
You suggest not using names as a primary key, and instead using auto numbers
or employee ID. I have a problem with, and maybe it's easy to solve and that
I'm just not thinking of it. So, I have one table with all my staff and an
employee ID and a second table with the employee ID and all the drill
information. When I go to enter new drills, I will either need to have all
employee IDs memorized or I will need to look at the other table to see what
the employee ID is. To me, this is creating more work. The reason I chose
to use first names was so that I don't have to memorize anything, and I just
type everything in without having to think. I have 80 staff, I really can't
try to memorize anything or have to look back each time to see what their ID
number is.
Click to expand...

Ummmm...

No.

You don't need to enter the ID.
You don't even need to SEE the ID!!!

It sounds like you're entering data directly into the table datasheet. That's
not how Access is designed to work!

Instead you would use a Form based on the table; on this Form you would have a
Combo Box which displays the employee's name, but stores the ID.

Use the tools that Access provides!!

You might want to look at some of these resources and tutorials, particularly
Crystal's video:

Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

Roger Carlson's tutorials, samples and tips:
http://www.rogersaccesslibrary.com/

A free tutorial written by Crystal:
http://allenbrowne.com/casu-22.html

A video how-to series by Crystal:
http://www.YouTube.com/user/LearnAccessByCrystal

MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
 
Thanks for the information. I'll give it a try. I think it's been too long
though since I last worked with Access, and I just end up frustrated.
 
John W. Vinson said:
Ummmm...

No.

You don't need to enter the ID.
You don't even need to SEE the ID!!!

It sounds like you're entering data directly into the table datasheet. That's
not how Access is designed to work!

Instead you would use a Form based on the table; on this Form you would have a
Combo Box which displays the employee's name, but stores the ID.

Use the tools that Access provides!!

You might want to look at some of these resources and tutorials, particularly
Crystal's video:

Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

Roger Carlson's tutorials, samples and tips:
http://www.rogersaccesslibrary.com/

A free tutorial written by Crystal:
http://allenbrowne.com/casu-22.html

A video how-to series by Crystal:
http://www.YouTube.com/user/LearnAccessByCrystal

MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
Click to expand...
 
Back
Top