Home |
Search |
Today's Posts |
#1
![]() |
|||
|
|||
![]()
{I'm merging HR data from an Excel spreadsheet into word letters. I've got a
number of date fields that I am merging. Consider you'll always have a start date for someone and you probably have their first pay rise but you may have a second, it is less likely you'll have a third one and so on. I've got the mergefields in a table and am using something like {MERGEFIELD "fieldnameX" \@ "dd-mmm-yy"} The dates appear as they should do on the first line of the word table but on all subsequent lines they revert to number of days since 1/1/1900 ignoring the formatting. Does anyone have any ideas what is happening. -- Paul |
#2
![]() |
|||
|
|||
![]()
Are you saying that where the data fields have no content that 1/1/1900 is
inserted instead? If that is the case you will have to test for content using a conditional field e.g. {IF{Mergefield fieldnameX \@ "yyyyMMdd"} 19000101 "{Mergefield fieldnameX \@ "dd-MMM-yy"}"} -- Graham Mayor - Word MVP My web site www.gmayor.com Word MVP web site http://word.mvps.org Paul - NottsUK wrote: {I'm merging HR data from an Excel spreadsheet into word letters. I've got a number of date fields that I am merging. Consider you'll always have a start date for someone and you probably have their first pay rise but you may have a second, it is less likely you'll have a third one and so on. I've got the mergefields in a table and am using something like {MERGEFIELD "fieldnameX" \@ "dd-mmm-yy"} The dates appear as they should do on the first line of the word table but on all subsequent lines they revert to number of days since 1/1/1900 ignoring the formatting. Does anyone have any ideas what is happening. |
#3
![]() |
|||
|
|||
![]()
Graham,
Thanks, I think I'd got there about the same time you suggested that, via your web site. I've been do some further tests by doing copy and paste values into a seperate worksheet and the issues appear different when the cell contains a formula and when it is apparently blank. I think this is a one of those instances where you ask when is a blank cell not a blank cell, when it contains a formula that resolves to the appearance of blank. I know you can use =na() but even that doesn't always give you what you you want when the field ends up in a mailmerge Thanks for your help. -- Paul "Graham Mayor" wrote: Are you saying that where the data fields have no content that 1/1/1900 is inserted instead? If that is the case you will have to test for content using a conditional field e.g. {IF{Mergefield fieldnameX \@ "yyyyMMdd"} 19000101 "{Mergefield fieldnameX \@ "dd-MMM-yy"}"} -- Graham Mayor - Word MVP My web site www.gmayor.com Word MVP web site http://word.mvps.org Paul - NottsUK wrote: {I'm merging HR data from an Excel spreadsheet into word letters. I've got a number of date fields that I am merging. Consider you'll always have a start date for someone and you probably have their first pay rise but you may have a second, it is less likely you'll have a third one and so on. I've got the mergefields in a table and am using something like {MERGEFIELD "fieldnameX" \@ "dd-mmm-yy"} The dates appear as they should do on the first line of the word table but on all subsequent lines they revert to number of days since 1/1/1900 ignoring the formatting. Does anyone have any ideas what is happening. |
Reply |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
zipcode problem with mailmerge using excel. | Mailmerge | |||
Mailmerge on word using excel data | Mailmerge | |||
enter an excel module global variable value in a mailmerge letter | Mailmerge | |||
mailmerge - excel datasource - other file extension? | Mailmerge | |||
Mailmerge from EXCEL, custom format problem | Mailmerge |