Word 2002 (XP) had the bug Bob Charest describes and today I see it again on my shiny new licensed and fully updated copy of Word 2013. My source data is in an Excel spreadsheet.

I've been Bingin' on the Internet but haven't found a solution yet, just workarounds. I appreciate the help from those who have suggested workarounds but I would like the root cause found and fixed. A workaround will only have me wondering "Why did I do this strange thing?" a month from now.