info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Outlook 2003 SP3 Autocorrect
4 views
Skip to first unread message
Ken
Sep 20, 2007, 3:58:06 PM9/20/07
to
After Office 2003 SP3 installed autocorrect no longer functions when using
Outlook as the email editor. It used to work when email was in Rich Text or
Plain text. It will work if I use Word as an editor. How do we fix this? I
have tried "detect and repair", turning off the autocorrect options and then
turning back on.
Outlook as the email editor. It used to work when email was in Rich Text or
Plain text. It will work if I use Word as an editor. How do we fix this? I
have tried "detect and repair", turning off the autocorrect options and then
turning back on.
Mary
Sep 20, 2007, 4:06:03 PM9/20/07
to
To restore Auto correct: (this is from OL Help)
From the main Microsoft Outlook window, on the Tools menu, click Options,
and then click the Spelling tab.
Select or clear the Use AutoCorrect when Word isn't the e-mail editor check
box.
From the main Microsoft Outlook window, on the Tools menu, click Options,
and then click the Spelling tab.
Select or clear the Use AutoCorrect when Word isn't the e-mail editor check
box.
Ken
Sep 20, 2007, 4:42:02 PM9/20/07
to
I have done all those multipled times on multiple PCs. This service pack has
disabled the function somehow.
disabled the function somehow.
neo [mvp outlook]
Sep 20, 2007, 5:35:18 PM9/20/07
to
FWIW, I can confirm it doesn't work under SP3. I've posted a message to the
other MVP's + a support board the MVPs have access to see if it is a known
issue. If I get any word from Microsoft, I will let you know. In the mean
time, best I can suggest is to call/report it to Microsoft Product Support
services since it is the service pack that appears to be the cause.
other MVP's + a support board the MVPs have access to see if it is a known
issue. If I get any word from Microsoft, I will let you know. In the mean
time, best I can suggest is to call/report it to Microsoft Product Support
services since it is the service pack that appears to be the cause.
"Ken" <K...@discussions.microsoft.com> wrote in message
news:BDD9B421-1A7B-4830...@microsoft.com...
0 new messages