Please Note: This article is written for users of the following Microsoft Word versions: 2007, 2010, 2013, and 2016. If you are using an earlier version (Word 2003 or earlier), this tip may not work for you. For a version of this tip written specifically for earlier versions of Word, click here: Proper Comparisons for Dates in Merge Fields.
Written by Allen Wyatt (last updated February 24, 2022)
This tip applies to Word 2007, 2010, 2013, and 2016
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 (9995) applies to Microsoft Word 2007, 2010, 2013, and 2016. You can find a version of this tip for the older menu interface of Word 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!
When you merge data from Excel into a Word document, you may need to do some conditional processing based on the data you ...
Discover MoreNeed to group records in some manner when they are used in a mail merge? It can be frustrating when your records are not ...
Discover MoreThe Mail Merge capabilities built into Word can appear limited at first glance. One thing that is often overlooked (and ...
Discover MoreFREE SERVICE: Get tips like this every week in WordTips, a free productivity newsletter. Enter your address and click "Subscribe."
2024-02-29 17:59:53
Jaime Carrozzi
Wouldn't this be simpler? { if {COMPARE { MERGEFIELD M_EXP \@ YYYYMMDD } < { DATE \@ YYYYMMDD } } = 1 "Yes" "No" }
Got a version of Word that uses the ribbon interface (Word 2007 or later)? This site is for you! If you use an earlier version of Word, visit our WordTips site focusing on the menu 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