Re: Search on Child Record Set

????

I agree that the quick example I chose to describe my question is not the most perfect piece of database design in the World. It was the first example that came to mind to describe the problem.

I simply assumed that EMP_SKILL has a foereign key to EMP and another column which is the skill's name. Why describe three entities when knowledge of two is enough to solve (or in this case describe) the problem?

Yes, this should, in any real life system, be an intersection entity but to describe it as such for the purposes of the problem at hand seemd a little superfluous at the time.

Thomas's solution made the right assumptions and has pojnted me in the direction I wanted.

Thanks Thomas (again!!!).

--
Alan D. Mills

Neil Hulin wrote in message <741ou2$fl1$3_at_newsreader5.core.theplanet.net>...
>
>EMP and EMP_SKILL is not a master-detail relation.
>EMP_SKILL is a 3nf intersecting entity.
>
>Consider...
>EMP[emp_id#,surname, first_name, middle_initial,
>emp_code]
>SKILL[skill_id#,skill_description, skill_code]
>EMP_SKILL[emp_id#, skill_id#]
>
>Trying to resolve this using the code below is WRONG
>and entirely unnecessary.
>
Received on Wed Dec 02 1998 - 04:58:43 CST