(Just noting that your second condition comapres something with itself)
YOu can use a nested IF. There's a limit to the number of levels and you
have to duplicate results. But e.g.
{ IF "{ MERGEFIELD FileCustomField15 }" = "FALSE"
"{ IF { MERGEFIELD FileCustomField7 } <> { MERGEFIELD FileCustomField7 }
"[... text passage #1]"
"[... text passage #2]" }" "[... text passage #2]" }
COMPARE returns 1 for a successful comparison, 0 otherwise. So you can AND
the results of two COMPAREs in an { = } field and test the result of that,
e.g.
{ IF { =and({ COMPARE "{ MERGEFIELD FileCustomField15 }" = "FALSE" },
{ COMPARE { MERGEFIELD FileCustomField7 } <> { MERGEFIELD
FileCustomField7 } }) } = 1
"[... text passage #1]"
"[... text passage #2]" }
You should be able to do more complicated and/or logic by nesting further
and(,) and or(,) functions.
Just make sure all the {} are the special field braces you can insert using
ctrl-F9
--
Peter Jamieson - Word MVP
Word MVP web site http://word.mvps.org/
> I've had no problems creating and using simple { IF Expression1 Operator
> Expression2 TrueText FalseText } merge codes but now I've plowed into a
[quoted text clipped - 43 lines]
>
> Rick
rtrsr - 19 Feb 2004 16:16 GMT
Ahhh. So THAT'S how you nest IF statements in this language! Once again,
Peter, your star burns ever brighter in the firmament!
Many, many thanks!!
Rick
PS > (Just noting that your second condition compares something with
itself) <
Uh, yeah... That's what happens when I try to type these commands in as
text. I got a little carried away with Word's Copy/Paste function. You're
quite right. A statement that "X <> X" might work in a Court of Law, but
not in any computer I've seen. So sorry for the confusion.
> (Just noting that your second condition comapres something with itself)
>
[quoted text clipped - 76 lines]
> >
> > Rick