Please Note: This article is written for users of the following Microsoft Word versions: 97, 2000, 2002, and 2003. If you are using a later version (Word 2007 or later), this tip may not work for you. For a version of this tip written specifically for later versions of Word, click here: Proper Comparisons for Dates in Merge Fields.
Written by Allen Wyatt (last updated June 10, 2017)
This tip applies to Word 97, 2000, 2002, and 2003
Volker is having a problem comparing dates in a merge field. His database contains a Birthdate field, which (obviously) contains a birth date for each person in the database. As he merges each record, he wants to compare the Birthdate field to a reference date, and then take some action based on the result. The logic he is attempting to use looks like this:
{IF {MERGEFIELD Birthdate} > "02/26/1981" "Under 30" "Over 30"}
The problem is that the comparison doesn't work properly; it doesn't return consistent results. One possible solution is to use a format switch in the merge field, in the following manner:
{IF {MERGEFIELD Birthdate\@"MM/DD/YYYY"} > "02/26/1981" "Under 30" "Over 30"}
This puts the incoming information into a comparable format. The results you get from this approach may depend, however, on characteristics of the data source, independent of Word. You could also try putting the dates into a year-first format, such as the following:
{IF {MERGEFIELD Birthdate\@"YYYY/MM/DD"} > "2011/02/26" "Under 30" "Over 30"}
If the comparison still yields inconsistent results, then the only solution may be to do a mathematical conversion on the date (actually, on both Birthdate and the reference date) so that you have an actual numeric comparison. You can do this by converting the date into a Julian value, which requires a very complex merge field, like the one shown here:
{IF {QUOTE {SET a{=INT((14-{MERGEFIELD BIRTHDATE \@ M})/12)}} {SET b{={MERGEFIELD BIRTHDATE \@ yyyy}+4800-a}} {SET c{={MERGEFIELD BIRTHDATE \@ M}+12*a-3}} {SET d{MERGEFIELD BIRTHDATE \@ d}} {SET jd{=d+INT((153*c+2)/5)+365*b+INT(b/4)-INT(b/100)+INT(b/400)-32045}} {jd \#,0}} > 2,443,056 "over 30" "under30"}
Such an approach may look intimidating, but is just the brute-force method necessary for some instances.
WordTips is your source for cost-effective Microsoft Word training. (Microsoft Word is the most popular word processing software in the world.) This tip (356) applies to Microsoft Word 97, 2000, 2002, and 2003. You can find a version of this tip for the ribbon interface of Word (Word 2007 and later) here: Proper Comparisons for Dates in Merge Fields.
Create Custom Apps with VBA! Discover how to extend the capabilities of Office 2013 (Word, Excel, PowerPoint, Outlook, and Access) with VBA programming, using it for writing macros, automating Office applications, and creating custom applications. Check out Mastering VBA for Office 2013 today!
One of the data sources that Word allows you to use for your mail merges is an Excel worksheet. You may get unexpected ...
Discover MoreWhen you get ready to merge a document with a data source, you'll want to make sure that everything is "as expected" ...
Discover MoreWhen you create a mail merge document, you attach it to a data source that is the basis for the information to be merged ...
Discover MoreFREE SERVICE: Get tips like this every week in WordTips, a free productivity newsletter. Enter your address and click "Subscribe."
2019-03-21 13:07:58
Alvaro Hernandez
After thinking for no more than 20 minutes, I came up with a simpler solution (that seems to work for my specific case , but I haven´t either thought carefully about it or tested it at length).
I do know I´m oversimplifying leap years and months that don´t have exactly 30 days.
It's like this:
{IF {QUOTE {SET a{={MERGEFIELD DATE \@ yyyy}*365+{MERGEFIELD DATE \@ MM}*30+{MERGEFIELD DATE \@ d} {a \# 0}} > 736866 "a" "b"}
The comparison should be done with the desired date, e.g., 09/26/2018 (2018*365+09*30+26 = 736866).
Any thoughts?
Thanks.
2019-03-21 08:06:57
Alvaro Hernandez
Dear Mr. Wyatt,
Thank you for your tips. They are really helpful.
However, as far as this tip goes, I´d like to suggest another review because it seems to me (and let me point out I´m not a proficient VBA programmer) that it may be in error. For instance, the year of the comparison date in the example changes from 1981 to 2011. Which is the correct one? In addition, can you please clarify whether the basis date for comparison (2,443,056) was obtained using the formulas you used for jd (cause I was not able to reproduce such result using either year). And last, but not the least, I tried using your tip and it did not work for me (assuming I've implemented it correctly).
Thank you for your time and great tips (which I often come across).
Got a version of Word that uses the menu interface (Word 97, Word 2000, Word 2002, or Word 2003)? This site is for you! If you use a later version of Word, visit our WordTips site focusing on the ribbon interface.
Visit the WordTips channel on YouTube
FREE SERVICE: Get tips like this every week in WordTips, a free productivity newsletter. Enter your address and click "Subscribe."
Copyright © 2024 Sharon Parq Associates, Inc.
Comments