Date format problem in Mail Merge - Word 2010

Anonymous
2011-05-04T05:45:56+00:00

How do you change the date format in Mail Merge - Word 2010?

In the data file the date is fomated as DD-MMM-YY, yet in the merge document it appears as MMM/D/YY?

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Paul Edstein 82,871 Reputation points Volunteer Moderator
2011-05-04T06:38:39+00:00

Word has a number of different methods of connecting to mail merge data sources, including DDE and OLE DB. Word 2002 and later use the OLE DB coonection by default, though you can change this (to DDE, for example). To work around a limitation in the OLE DB provider used to get data from Excel etc., when Word is connected to an OLE DB data source, it treats dates as if they are in the US mm/dd/yy format, regardless of the format in Excel, your regional settings etc. Applying a date format switch fixes that - and gives the mailmerge document the ability to format the date independently of whatever format is used in the data source.

To get the date format you want, you can add a formatting picture switch as follows:

• select the mergefield;

• press Shift-F9 to expose the field coding. It should look something like {MERGEFIELD MyDate} where 'MyDate' is your mergefield's name;

• delete anything appearing after the mergefield's name and add '@ "dd-MMM-yy"' to the field, as in {MERGEFIELD MyDate @ "d MMMM yyyy"}. With this switch your date will come out as '2 August 2008'. Other possible date formatting switches include:

. @ "dddd, d MMMM yyyy";

. @ "ddd, d MMMM yyyy";

. @ "d MMM yyyy";

. @ "dd/MMM/yyyy".

Note: Note: you can swap the d, M, y expressions around, but you must use uppercase 'M's for months - lowercase 'm's are for minutes.

• position the cursor anywhere in this field and press F9 to update it;

• run your mailmerge.

Was this answer helpful?

700+ people found this answer helpful.
0 comments No comments

78 additional answers

Sort by: Newest
  1. Paul Edstein 82,871 Reputation points Volunteer Moderator
    2015-11-08T07:31:21+00:00

    Problem: Even with field codes properly set up such as:

    {MERGEFIELD MyDate @ "dd MMMM yyyy"}

    the date still displays like 42238 in the MS Word mailing document.

    ....

    So the original source spreadsheet is also very important.

    True. However, my post of October 27, 2014 showed how to deal with that scenario in situations where changing the data isn't a viable option.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-11-08T07:10:53+00:00

    Dear Paul

    I followed your guidance and it worked from the first time

    Many thanks for your support

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-08-22T13:13:02+00:00

    Just to add to the good answer by macropod:

    Problem: Even with field codes properly set up such as:

    {MERGEFIELD MyDate @ "dd MMMM yyyy"}

    the date still displays like 42238 in the MS Word mailing document.

    Answer: In the Excel (2013) spreadsheet the column looked like:

    MyDate            <- Column header in row 1

    Date of letter   <- Non recognisable date in row 2 caused the error

    21/07/2014

    22/08/2015

    .....

    After changing the second row to 01/01/2000, the MergeField formatting worked correctly, displaying as 22 August 201 5.

    MyDate

    01/01/2000

    21/07/2014

    22/08/2015

    ....

    So the original source spreadsheet is also very important.

    Hope you don't get stuck too long also.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-03-18T10:14:24+00:00

    Thanks for that - been scratching my head for 2 days now....

    Was this answer helpful?

    0 comments No comments