A family of Microsoft word processing software products for creating web, email, and print documents.
Hi All:
This is one of those maddening posts that does not contain the answer (just thought I would get this in up-front...)
It would appear that there are two issues:
Hannah has (or had) a flaky file corruption which I suspect was a defect in the .rels file.
The other three seem to have a simple broken file.
If Doug had been able to get a look at Hannah’s “pre-red-X file” we would have had a better chance. I note that Hannah said she was using .TIFF files while her picture folder when Doug got in there displayed .EMZ files. I also remember that early versions of Word could not handle 48-bit TIFF files; you needed to tell the users very explicitly to ensure they did not insert anything higher than RGB (24-bit) TIFFs.
The only thing I could suggest is IF you can get hold of a pre-red-x copy of the document, save it out to .doc or RTF format in the “good” copy of Word, and re-save the RTF as .docx in the latest version of Word. This would re-write all the coding and linking and fix the file. But if you can’t get hold of an unbroken copy of the file, it’s too late to try that.
How did it happen? Who knows: but one thing almost guaranteed to cause this kind of trouble is switching between versions of Word (e.g. Word 2010 to Word 2016 and back...) frequently. Going out to open-source word-processors is another fertile source of this bother.
I'm a Mac Word MVP: The reference to Mac Word should increasingly not matter: there has been a major change to Mac Word in version 2016. The code base for Office 2016 on the Mac is now the 64-bit version of the exact same code as Windows Office 64 is running. On the Mac, various bits are currently turned off so they can present them as {Gasp! Amazement!!} “New Features” in Office 365. But it’s now the same code both sides of the divide. iOS and iPhone are, of course, different…
Sorry I can't be more definitive without a look at the file ...