
Signature
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP
My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Thanks Graham. I did manage to get it to work however I had to change the SET
DELAY to 42! I suspect that this is because, when it was left at 14, it is
taking 14 days away from a proper, created date field, therefore making the
result 28 days in the past rather than 14 days in the future. This is what
one of our lead programmers thought. I have decided instead to use the word
system date, which obviously works. I do have a question on that though: the
first time I used this code, the future date used to come through on the
finished merged documents as a mergefield, much like { DATE } does, and would
change when you opened the document a few days later. This doesn't seem to be
happening now, and the future date seems hard coded to the merged document.
Has something changed within the code, or do newer versions of word handle
this type of programming differently?
Thanks.
Regards,
Chris
> If { MERGEFIELD YYYCZ1 } produces a date with the ordinal, there is no way
> that you can use the calculated fields to produce a future date. Word fields
[quoted text clipped - 27 lines]
> > yy{=100*e+g-4800+INT(i/10)}}{=dd*10^6+mm*10^4+yy \# "00'-'00'-'0000"}
> > \@ "dddd, d MMMM yyyy"}
Graham Mayor - 29 May 2008 06:29 GMT
I suspect the problem is simply a reluctance to automatically update a
calculated field on a document that has been re-opened. However if you merge
the document, the calculated field in the merged document is converted to
text and so cannot be updated.

Signature
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP
My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
> Thanks Graham. I did manage to get it to work however I had to change
> the SET DELAY to 42! I suspect that this is because, when it was left
[quoted text clipped - 56 lines]
>>> yy{=100*e+g-4800+INT(i/10)}}{=dd*10^6+mm*10^4+yy \#
>>> "00'-'00'-'0000"} \@ "dddd, d MMMM yyyy"}
Chris Stammers - 30 May 2008 12:48 GMT
Thanks Graham. It's far from a problem, because I never wanted the date to
change anyway!
Regards,
Chris
> I suspect the problem is simply a reluctance to automatically update a
> calculated field on a document that has been re-opened. However if you merge
[quoted text clipped - 61 lines]
> >>> yy{=100*e+g-4800+INT(i/10)}}{=dd*10^6+mm*10^4+yy \#
> >>> "00'-'00'-'0000"} \@ "dddd, d MMMM yyyy"}