With recent updates, whenever I change the style of selected text, word
applies it to the whole doument. I then have to undo the "Auotomatically
Update Style" to remove the global changes, leaving just the change I want.
E.g. if I change the text color or apply bullets to a single line, the whole
document changes.

Whilst the work round is OK, up to a point, after a while the undo fails
(too manu format changes). Closing and reopening the file doesn't help and I
have to select everything and copy it to a new document form time to time.
The document is only 4 pages, but does use 4 text colors and 3 or 4 different
font sizes.

There's a similar problem with outlook (using Word as the Editor), when
replying to a message in RTF format. The whole document left aligns and
converts to the same font and color. I need to undo to get the format back.

The problem started after a recent fix was applied, but probably before SP2.

Clear the "Automatically update style" option of the affected style
(usually Normal) and then add the new style definition to the
template. See
http://word.mvps.org/FAQs/Formatting...eformatted.htm

--
Stefan Blom
Microsoft Word MVP


"david57" wrote in message
...
With recent updates, whenever I change the style of selected text,
word
applies it to the whole doument. I then have to undo the
"Auotomatically
Update Style" to remove the global changes, leaving just the change
I want.
E.g. if I change the text color or apply bullets to a single line,
the whole
document changes.

Whilst the work round is OK, up to a point, after a while the undo
fails
(too manu format changes). Closing and reopening the file doesn't
help and I
have to select everything and copy it to a new document form time to
time.
The document is only 4 pages, but does use 4 text colors and 3 or 4
different
font sizes.

There's a similar problem with outlook (using Word as the Editor),
when
replying to a message in RTF format. The whole document left aligns
and
converts to the same font and color. I need to undo to get the
format back.

The problem started after a recent fix was applied, but probably
before SP2.