Simple example:
1:n relationship and create the following query.
Name Course
John A
John B
John C
Sarah A
Sarah C
Sarah D
Phil B
Phil C
Phil D
I now know that
Course A was attended by John and Sarah
Course B was attended by John and Phil
Course C was attended by John, Sarah and Phil
Course D was attended by Sarah and Phil
If there is anything wrong with this please let me know.
"Allen Browne" wrote:
Clearly, I have no idea what you are talking about either.
If your tables have no foreign keys, you can do what you like.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"scubadiver" wrote in message
...
But that doesn't mean to say I can't list all the employees who have taken
a
specific course? If establishing a 1:n relationship between course and
employee means it could be quicker to enter information into a form, then
there is a trade off.