Products: Word 2016 (for Mac) and Outlook 2016 (for Mac) - the apps, not the browser clients. PROBLEM: Word 2016's SPELL CHECK (as you type) feature does not work on docs that arrive in Outlook as attachments. Steps to Replicate: Receive an email in Outlook 2016 for Mac with a Word attachment. Open the attachment, and Word will alert you to the fact that the document before you is READ-ONLY (this, I suspect, because it remains a static part of Outlook's local mail database). When you Save As and begin editing the Word document, the squiggly red lines of the spell checker do not appear. Troubleshooting: I discovered that if I copy the text of the Word file into a new, blank Word doc, the spell check with the squiggly lines immediately works. ![]() I switched over to Apple's native MAIL app instead of Outlook and did the same thing, only to discover that the spell check works immediately (with or without using the SAVE-AS feature; it appears to me MAIL allows Read/Write access to Word attachments stored in its Db). This suggests strongly to me that the problem is in the way Outlook handles attachments. Choose Edit→Spelling and Grammar→Check Document Now, or press Command-semicolon to advance to the next flagged mistake without using the dialog. In the Message Compose window, select the Options tab of the Ribbon, and click the Spelling button to display the Spelling and Grammar dialog. I have not been successful finding any record of this problem/issue being posted before (which I'm sure is not possible; my own search skills are clearly at fault). Camtasia studio vs camtasia for mac. I did find on Spiceworks, but the issue described had no parallels with the issue I'm wrestling with and is over a year old. Any help or insight you might provide would be greatly appreciated!! Thank you for reading this. Dave Edited Jun 20, 2017 at 00:32 UTC. Its my understanding that the repair tool is Windows/PC only, and that the Mac 'version' of this is a complete/ lean reinstall of Office 2016/365. I am currently holding off doing this because 1) the user has years of emails accumulated so that it takes over a day for a new instance of Outlook 2016 for Mac to rebuild its database, and 2) since I don't know what the nature of the problem is yet, I'm loathe to undertake such a time-consuming enterprise. If you have further suggestions pertaining to Mac-based deployments, please let me know. And thank you for taking the time to respond!
0 Comments
Leave a Reply. |