Re: CL: Identifying the 'real' message.

I understand what you are saying in your first paragraph. I am hoping
that doesn't apply in something that happens in a tight bundle of code
versus something that is wrapped around another program that is called.
I can also see where a loop may be necessary in a close example. Like,
using SUBTREE(*ALL). In which the exception may be some changed some not
and I'd have to loop to find the ones that weren't.

Rob Berendt