M
Matt M
Hi folks,
Our users are suffering the problems outlined in KB 912940
(http://support.microsoft.com/kb/912940/en-us). Whilst the workarounds listed
in that article work fine their flaw is that they are of little relevance if
we email a Word document out to a client. With Word's default behaviour being
to open .doc email attachments into Reading Layout our clients are seeing
dodgy contents tables and without any knowledge of KB 912940 would likely
just think we can't even create a working contents page. Note that a
recipient opening an attachment into Reading Layout and then selecting
"Normal" or "Print Layout" from the View menu won't see a fixed contents page
- the Reading Layout will permanently break the contents page regardless of
View menu setting, unless formatting changes are rejected (something we can't
expect our recipients to necessarily do).
The very last paragraph in KB 912940 actually seems to be wrong, we've
tested this on multiple computers but would be interested in seeing other
people's experiences.
Thus far our only workarounds have been to package files in a zip file
before attaching to an email, or of course converting to a PDF file. Anyone
else have any workarounds they find work?
Cheers,
Matt
Our users are suffering the problems outlined in KB 912940
(http://support.microsoft.com/kb/912940/en-us). Whilst the workarounds listed
in that article work fine their flaw is that they are of little relevance if
we email a Word document out to a client. With Word's default behaviour being
to open .doc email attachments into Reading Layout our clients are seeing
dodgy contents tables and without any knowledge of KB 912940 would likely
just think we can't even create a working contents page. Note that a
recipient opening an attachment into Reading Layout and then selecting
"Normal" or "Print Layout" from the View menu won't see a fixed contents page
- the Reading Layout will permanently break the contents page regardless of
View menu setting, unless formatting changes are rejected (something we can't
expect our recipients to necessarily do).
The very last paragraph in KB 912940 actually seems to be wrong, we've
tested this on multiple computers but would be interested in seeing other
people's experiences.
Thus far our only workarounds have been to package files in a zip file
before attaching to an email, or of course converting to a PDF file. Anyone
else have any workarounds they find work?
Cheers,
Matt