Hi Contro,

I've looked at the example, and indeed your message, again and realised
I read it all wrong! I'm sorry for that; I guess I was not as alert
since it was a Saturday (I'm sticking to that excuse!).

Thank you very much, I'll try out that example on Tuesday when I'm back
with the database, and will let you know the results! I don't know why
some of the old code isn't there anymore, but I'm guessing the "1"
mentioned is just a way of expressing that the keys match. At any
rate, if it works, that is all that matters!

I'm sorry I didn't formulate my response any more clearly; my head was
trying to deal with correcting the link on my website and answer you...

When I looked at the example you showed me and saw the "NextIF" field,
the alarm bells went off. SkipIf and NextIf are "deprecated" (to use MS
parlance for things they don't support any more). Once you dig into the
newer article I think you'll find it makes more sense when thinking in
terms of a key field.

The key value of the current record will be compared against the value of
the last record (which is why the records have to be sorted according to
key field in the data source). If the two match, the part of the IF will
be executed that creates the list. If they differ, then it put out the
text for the "one" side of the equation.

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 :-)