track changes and header problem

From: Rob (rob_at_nospam.com)
Date: 03/20/04 

Date: Sat, 20 Mar 2004 10:28:13 -0500

I googled for this and saw many others with this problem. While there were
a couple of suggestions on how to fix this, there were no clear answers and
none of the suggestions worked for me.

Problem: Running 2000 with tracking changes enabled. I accept all changes,
but the header still shows deleted text and the revised text (the header is
a field code of {STYLEREF "Heading 1"} )

I've shut off tracking and tried to accept everything, I've updated the
field with tracking off and locked it (shift F11). As soon as I turn
tracking on, these fields again show the changes made previously. I need to
send this out to a customer and am just trying to remove the last remnants
of changes shown. Any help is greatly appreciated, thanks!

Relevant Pages

  • Re: Tracking SirCam
    ... Subject: Tracking SirCam ... there is a slip -- the Date: header actaully ... | case 'date:' for the header are sent by the SirCam virus. ... but one of these I've seen came through mail lists, ...
    (Incidents)
  • Re: track changes and header problem
    ... Don't turn on change tracking after updating the document - As soon as ... anything causes the header/footer to update, they'll register a change. ... > but the header still shows deleted text and the revised text (the header ...
    (microsoft.public.word.pagelayout)
  • Tracking SirCam
    ... Subject: Tracking SirCam ... Trying to track the SirCam virus without looking at the body of the ... In the header of the message, everything looks dynamic, and so tracking it ... Senior System Administrator ...
    (Incidents)
  • Re: Tracking SirCam
    ... Subject: Tracking SirCam ... Peter Krawczyk wrote: ... the virus engineers its own SMTP header. ... Is the FROM: information correct? ...
    (Incidents)
  • Re: KB942615 is Defective and Microsoft Advisies Removing and Disa
    ... been tracking issues in CSS Security as well. ... Thank you for letting us know that MSRC knows and sees these posts and have ... that the below link to this registry fix does ... thanks for the info - I think I will wait for the next update to fix ...
    (microsoft.public.windowsupdate)