table joins

Big time! Thanks for catching that -- no foreign key, no Parent! Don't you
just love the brain power the groups bring!

I must have gotten so wrapped up in detail that I forgot the forest.

Regards

Jeff Boyce
Office/Access MVP

"tina" wrote in message
...
Jeff, PMFJI, but...in tblCorrectiveAction, are you missing the foreign key
field IncidentID from tblIncidents? (or maybe i'm missing something...)


"Jeff Boyce" wrote in message
...
Tim

Again, perhaps because I'm not there and can't see what you're working
with,
this is just one person's opinion...

tblIncident (this table holds information about incidents)
-IncidentID (a Primary Key, an Access Autonumber, unless you have an
incident reporting system that creates a unique identifier for each
incident)
-IncidentCategory (Quality, Safety, ... -- you could create another
table to hold IncidentCategory, then use that here)
-DateReported
-ReportedBy (you could create another table to hold the folks who
can
report, referred, get referred to, carry out corrective action, etc.,
then
use it everywhere you'd need a person)
-IncidentDescription
-DateReferredForAction
-ReferredTo
-ReferredBy
-(... any other characteristics of the incident that you need to
keep
track of)

trelCorrectiveAction (the table that tracks what gets done)
-CorrectiveActionID (Primary Key, ... see above...)
-ActionDate
-ActionTakenBy
-ActionDescription
-OriginalReporterContacted (this was my own invention -- letting the
original caller know what happened)
-(... any other characteristics of the Corrective Action that you
need
to keep track of)

Once you have your data in tables like these (and any other
supporting/lookup tables, i.e., persons, incident categories, etc.), you
can
create queries to join corrective action(s) to incident. You can use
forms
for collecting both the incident and the related corrective action(s).
You
can use reports to print out detail or summary of incident and action.

Hope that helps...

Regards

Jeff Boyce
Office/Access MVP