I'm also using Word 2016 and that xref field in your sample doc refreshes correctly to show 1.2.2



I don't know of any option settings that might break this xRef on your machine.

Does it make a difference if you change the compatibility mode of the document?
What happens if you edit the xRef field to remove the '\* MERGEFORMAT' switch?

__________________
Andrew Lockton
Chrysalis Design, Melbourne Australia

Thanks for your comments. I will ask my husband to test out your ideas. By the way, the same problem exists on old documents on his machine too. We share a Dropbox but I don't think that is infecting the documents. Perhaps it is in the merge switch.

All I can think of since it worked for years and now doesn't is that I enabled/disabled something that affects the docs.