Hi Contro,

http://support.microsoft.com/?kbid=105888

which I do believe gives a solution to the problem, but I don't
understand it enough to change it to my context.

If you aren't comfortable with Doug's suggestions, tell us where
you're getting stuck with the technique described in the KB
article.

To describe in laymen's terms the underlying principle:

Each "main entry" (the student) must be uniquely identifiable
(usually something like an ID field). All the "sub entries" that
belong to the main entries must also contain this field.

The data must be sorted on this field, so that all the entries
for an individual are grouped together. this means the mail merge
will process the records in exactly this order.

The complex field set the KB article postulates picks up this ID
field when record is merged. It assigns this value to a "holding
tank" at the end of the record merge. At the beginning of the
record merge, these two values are compared. If they match, then
the "list" part of the IF field is executed. If they do not
match, then the "main entry" part of the IF field is executed.

The tricky part when setting this up is usually understanding how
it's supposed to work, and then getting the "main" and "list"
parts into the IF field correctly.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8
2004)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow
question or reply in the newsgroup and not by e-mail :-)