Results 1 to 6 of 6
  1. #1
    3 Star Lounger
    Join Date
    Aug 2002
    Location
    Phoenix, Arizona, USA
    Posts
    205
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Auto Correct (Word 2003 SP3)

    I have a user who adds a carbon copy as cc: and it always comes out as Cc: I have tried everything I know to stop this and the only thing that works is to uncheck capitalizing the first letter of a sentence. That causes its own problems. Is there another way to stop this?

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Auto Correct (Word 2003 SP3)

    Have you tried adding cc: to the list of exceptions in Tools | AutoCorrect Options...?

  3. #3
    3 Star Lounger
    Join Date
    Aug 2002
    Location
    Phoenix, Arizona, USA
    Posts
    205
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Auto Correct (Word 2003 SP3)

    Yes, I have. When adding the colon to the cc, I cannot add to the exceptions.

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Auto Correct (Word 2003 SP3)

    You're correct, sorry <img src=/S/sorry.gif border=0 alt=sorry width=15 height=15>

  5. #5
    2 Star Lounger
    Join Date
    Jul 2001
    Location
    London, Gtr London, England
    Posts
    100
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Re: Auto Correct (Word 2003 SP3)

    In autocorrect, preface "cc" with, say, "#", and set it so that "#cc" is autocorrected to "cc". [omit the quote marks]

    Seems to work on Word 2007, which is what I have to hand at the moment.

    Regards
    Will

  6. #6
    3 Star Lounger
    Join Date
    Aug 2002
    Location
    Phoenix, Arizona, USA
    Posts
    205
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Auto Correct (Word 2003 SP3)

    This works beautifully, but I do not know if the user will want to add the #cc: It seemed to be the colon after the cc that caused the problem, but adding the # sign does the trick. Than you so much for helping me with this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •