Hi Cindy,

Thanks for you reply. My database is fully normalised (so far as is
required anyway! I'm no expert on it, but it's all up so the
relationships are right and the primary and foreign keys are in place).

The code of the knowledge base example is:

Employee Project
{MERGEFIELD Employee} {MERGEFIELD Project}{set duplicate {if
{MERGEFIELD Check}="1" "off" "on"}}{nextif {mergefield check}=""}{if
{duplicate}="on" "P
t{MERGEFIELD Project}"}{set duplicate {if {MERGEFIELD Check}="1"
"off" "on"}}{nextif {mergefield check}=""}{if {duplicate}="on" "P
t{MERGEFIELD Project}"}{set duplicate {if {MERGEFIELD Check}="1"
"off" "on"}}{nextif {mergefield check}=""}{if {duplicate}="on" "P
t{MERGEFIELD Project}"}{set duplicate {if {MERGEFIELD Check}="1"
"off" "on"}}{nextif {mergefield check}=""}{if {duplicate}="on" "P
t{MERGEFIELD Project}"}

From what you mention, I see that the code basically looks for items
which have a primary key - foreign key match (subjects that belong to
the same student). I'm just not sure how to use this code to my
situation though. Above, the code seems to be looking for a number in
a "check" table which is 1; I've no idea why. Also, I do not
understand all the "off" "on" business at all or how they relate to the
"1" that is specified and whether they need to relate to a 1, or if
this is just something that is only part of this example and isn't
necessary (not something I'd need to use in my own database).

Basically, I'm lost! Please help! :-)

Contro.