[Peter Jamieson]

Thanks Graham - I was using 2007 but will try 2003 now.

--
Peter Jamieson
http://tips.pjmsn.me.uk

"Graham Mayor" wrote in message
...
Hmmmm. I couldn't get it to work in Word 2003 - though I didn't have the
quotes around "{ MERGEFIELD mydatetext }"
I'll play again tomorrow

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org


Peter Jamieson wrote:
OK, it certainly works here, i.e. in principle, so maybe the detail
needs checking:

preferably with a space
between month and year.

I suspected as much :-)

{ SKIPIF "{ MERGEFIELD mydatetext }" "{ DATE \@"D" \*Ordinal }{
DATE \@" MMMM YYYY" }" }

works OK here with that spec. All the {} have to be ctrl-F9 braces as
usual, and the spacing and quoting is obviously import -

either one space between the two DATE fields and

\@"MMMM YYYY"

or no space between the two DATE fields and

\@" MMMM YYYY"


"gjupp via OfficeKB.com" u41094@uwe wrote in message
news:7f606d68464d2@uwe...
Yes, this is the comparison that I wish to make, preferably with a
space between month and year. And yes, we wish to make a 'not equal'
comparison. I tried your suggestion, but the merge returned nil results.
Word
date format
(language 'English (UK)') was set to 'dd MMMM yyyy' without ordinal.
However,
this may have no relevance.

Unless your suggested SKIPIF syntax can be modified, I suppose it
will not be
possible to achieve my aim. If so, I shall continue to use SKIPIF
with the comparison date manually inserted at each merge. This will
be crude, but the
method will work.

Many thanks indeed for your advice. It is very useful.



Peter Jamieson wrote:
You mean compare with things that are in your data source like

7th February2008
1st March2008

etc?

As long as you can use date and numeric field switches that generate
precisely the date format you need to compare with, you should be
able to use a simlar technique, e.g.

{ SKIPIF "{ MERGEFIELD mydatetext }" "{ DATE \@"D" \*Ordinal }{
DATE \@"
MMMMYYYY" }" }

Haven't tried it myself though, and at best you will only be able
to do exact comparisons (equal or not equal), not determine whether
one date is before the other.

Many thanks indeed. This works fine. However, to go one step
further: Is it
[quoted text clipped - 11 lines]

Many thanks in anticipation.

--
Message posted via http://www.officekb.com