Microsoft word switch over

can i transfer microsoft word files from my PC to my mac mini? do i have to buy microsoft office for mac to do this, because i don't think i want to do that. i so, can i change the format of my microsoft documents to put them on mac mini?

Interesting solution Ganz. At first I thought you were talking about thinkfree Office, but this online thing is rather unexpected. However, as you pointed out, it's probably only good for occasional work.
As for OpenOffice (which has already been mentioned in this post), you will have to get the right version for your Mini. If i'ts a new one, then you will have to get an Intel Build. You can find one on this page. OpenOffice.org (X11) for Mac OS X will not look and feel like a standard Mac OS X application, but I've found its compatibility with MS Office documents very good (actually, I use NeoOffice, which is based on OOo/X11, with a more Mac-like interface - the underlying code is the same except for the UI, although NeoOffice, being based on OOo/X11's code, is usually a bit behind in terms of features, and on the other hand is much more integrated with OS X - but there is no Intel build of NeoOffice yet) ...

Similar Messages

Somehow the Spelling/grammar check in Microsoft Word switched to French. How do I switch it back?

Somehow the Spelling/grammar check in Microsoft Word switched to French. How do I switch it back?

In the Word menu bar, click Tools and select Language. Make your changes there:

Microsoft word stops responding when i open a document

This has been happening on and off for ages, from half a year to a year. I have been trying to open a document for 4 hours now, it opens it and then freezes, i then have to force quit it and start over again. Some times i have left it for a while others i quit it after it stops responding. It is getting ridiculous now, i have also searched for ages on the internet, some problems are unrelated some seem related but the fixes don't work, I need help to get word to stop doing this.
I thought maybe it was because it keeps opening all my previous documents that I had open, i unchecked the box so it doesn't reopen windows and it still freezes but on this document instead. I do not have a clue what to do and I urgently need access to these documents, the documents aren't damaged, i was working on them before, and had this problem with many other documents that also weren't damaged. What should I do? I do not have a clue and it's been a truly annoying problem for a long time now.

Hello, I did as you asked, I hope this isn't too many lines i put. I don't understand any of it and so I don't know what is needed, but this doesn't have over 50 lines so i thought it may be okay. I can't see my name in my log so it seems okay from that point of view. Thanks for your help, this problem has been driving me nuts, i don't know if i've done anything or this is just because of gradual ware and tear as my macbook is the last one they produced. But i wouldn't think its software would have suffered much ware and tear to become that outdated already.
10/09/2014 16:34:30.605 gkbisd[176]: Unable to collect cdhash for /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.f ramework/Versions/A/Resources/QuickLookUIHelper.app (error code 100024)
10/09/2014 16:34:32.956 gkbisd[176]: Unable to collect cdhash for /Applications/Microsoft Office 2011/Microsoft Word.app (error code 100024)
10/09/2014 16:34:45.193 WindowServer[98]: disable_update_timeout: UI updates were forcibly disabled by application "Microsoft Word" for over 1.00 seconds. Server has re-enabled them.
10/09/2014 16:34:47.346 WindowServer[98]: common_reenable_update: UI updates were finally reenabled by application "Microsoft Word" after 3.15 seconds (server forcibly re-enabled them after 1.00 seconds)
10/09/2014 16:34:53.000 kernel[0]: memorystatus_thread: idle exiting pid 83898 [spindump_agent]
10/09/2014 16:34:53.585 com.apple.launchd.peruser.501[214]: (com.apple.spindump_agent[83898]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
10/09/2014 16:34:53.585 com.apple.launchd.peruser.501[214]: (com.apple.spindump_agent[83898]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
10/09/2014 16:34:53.000 kernel[0]: memorystatus_thread: idle exiting pid 83906 [CloudKeychainPro]
10/09/2014 16:34:53.857 secd[83905]: handle_xpc_event >>>>> handle_connection_event via event_handler <<<<<, ***?
10/09/2014 16:34:53.859 com.apple.launchd.peruser.501[214]: (com.apple.security.cloudkeychainproxy3[83906]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
10/09/2014 16:34:53.859 com.apple.launchd.peruser.501[214]: (com.apple.security.cloudkeychainproxy3[83906]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
10/09/2014 16:34:54.000 kernel[0]: memorystatus_thread: idle exiting pid 83905 [secd]
10/09/2014 16:34:54.133 WiFiKeychainProxy[83904]: xpc __securityd_create_connection_block_invoke got event: Connection interrupted
10/09/2014 16:34:54.143 com.apple.launchd.peruser.501[214]: (com.apple.secd[83905]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
10/09/2014 16:34:54.144 com.apple.launchd.peruser.501[214]: (com.apple.secd[83905]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
10/09/2014 16:34:54.000 kernel[0]: memorystatus_thread: idle exiting pid 83872 [syncdefaultsd]
10/09/2014 16:34:54.398 com.apple.launchd.peruser.501[214]: (com.apple.syncdefaultsd[83872]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
10/09/2014 16:34:54.398 com.apple.launchd.peruser.501[214]: (com.apple.syncdefaultsd[83872]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
10/09/2014 16:34:54.000 kernel[0]: memorystatus_thread: idle exiting pid 83907 [com.apple.iCloud]
10/09/2014 16:34:54.647 com.apple.launchd[1]: (com.apple.iCloudHelper[83907]) Exited: Killed: 9
10/09/2014 16:34:54.000 kernel[0]: memorystatus_thread: idle exiting pid 83903 [backupd-helper]
10/09/2014 16:34:54.862 com.apple.launchd[1]: (com.apple.backupd-auto[83903]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
10/09/2014 16:34:54.862 com.apple.launchd[1]: (com.apple.backupd-auto[83903]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
10/09/2014 16:34:55.000 kernel[0]: memorystatus_thread: idle exiting pid 83904 [WiFiKeychainProx]
10/09/2014 16:34:55.120 com.apple.launchd.peruser.501[214]: (com.apple.wifi.WiFiKeychainProxy[83904]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
10/09/2014 16:34:55.120 com.apple.launchd.peruser.501[214]: (com.apple.wifi.WiFiKeychainProxy[83904]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
10/09/2014 16:34:55.000 kernel[0]: memorystatus_thread: idle exiting pid 83868 [com.apple.CodeSi]
10/09/2014 16:34:55.377 com.apple.launchd[1]: (com.apple.CodeSigningHelper[83868]) Exited: Killed: 9
10/09/2014 16:34:55.000 kernel[0]: memorystatus_thread: idle exiting pid 83879 [com.apple.IconSe]
10/09/2014 16:34:55.638 Finder[49278]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted
10/09/2014 16:34:55.638 Finder[49278]: XPC error messaging com.apple.IconServicesAgent: Connection invalid
10/09/2014 16:34:55.674 com.apple.launchd[1]: (com.apple.IconServicesAgent[83879]) Exited: Killed: 9
10/09/2014 16:34:55.712 Console[83864]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted
10/09/2014 16:34:55.713 Console[83864]: XPC error messaging com.apple.IconServicesAgent: Connection invalid
10/09/2014 16:34:55.888 Microsoft Word[83909]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted
10/09/2014 16:34:55.889 Microsoft Word[83909]: XPC error messaging com.apple.IconServicesAgent: Connection invalid
10/09/2014 16:34:57.417 WiFiKeychainProxy[83915]: [NO client logger] <Nov 10 2013 18:30:13> WIFICLOUDSYNC WiFiCloudSyncEngineCreate: created...
10/09/2014 16:34:57.417 WiFiKeychainProxy[83915]: [NO client logger] <Nov 10 2013 18:30:13> WIFICLOUDSYNC WiFiCloudSyncEngineRegisterCallbacks: WiFiCloudSyncEngineCallbacks version - 0, bundle id - com.apple.wifi.WiFiKeychainProxy
10/09/2014 16:34:58.115 _usbmuxd[83923]: audit warning: soft /var/audit
10/09/2014 16:34:58.116 _usbmuxd[83922]: audit warning: closefile /var/audit/20140910153252.20140910153457
10/09/2014 16:34:58.117 _usbmuxd[83921]: audit warning: allsoft
10/09/2014 16:34:59.513 xpcproxy[83926]: assertion failed: 13E28: xpcproxy + 3438 [D559FC96-E6B1-363A-B850-C7AC9734F210]: 0x2
10/09/2014 16:34:59.986 com.apple.iCloudHelper[83926]: AOSKit ERROR: ((null)) Cannot refresh account bag, missing acct info (user=.dat00a5.000, hasPassword=0)
10/09/2014 16:35:03.670 syncdefaultsd[83925]: Fixing push token

Advange of using Adobe Acrobat over Microsoft word 2007 PDF add -in

Hi,
I would like to know what is the advantage of using Adobe Acrobat 9 standard or professional over Microsoft Word 2007 PDF addin. Microsoft will ship the PDF convertor with SP2 later this month, in that case what should be the use of using adobe acrobat to convert a document to PDF and not use microsoft word built in features.
This is just a doubt which arouse and thought if I could ask here, thought to control some adobe acrobat licenses being used in our environment.
Rgds
Rahul Goel

I have found that some of the links and other items just to not work well with the add-in from MS. However, with OFFICE 2007, it appears that MS has put some hooks in the system to screw up Acrobat. Typical pages that are produced with Acrobat get cut into sections (a graphic will be chopped into multiple graphics and pasted together). I say this is OFFICE only from the perspective that we have tried it with OFFICE 2007 and both AA7 and AA8 and gotten the same result. When we used the same file in OFFICE 2003 with AA7, the PDF was fine. So when you complain about the PDFs created by OFFICE 2007 and Acrobat, you may be seeing something that is a result of OFFICE, not Acrobat. Generally they still look good, it is only in some detail where you will see problems.
A major advantage we found with Acrobat is that it did not have issues with messing up the links that the MS add-in had. You can try some of this yourself, but that is a summary of our conclusions. Bill

How to prevent Microsoft word from switching which desktop I am on?

I have a 2011 Macbook Pro, OSX Version 10.9.2 as well as microsoft word for mac 2011 (the most recent update). I have had an issue for a number of years where when I have microsoft word open in one desktop and am using another application in another desktop, I will automatically jump back to the desktop with microsoft word without doing anything. I am then forced to switch between desktops back to the desktop I was on before. It's obviously pretty obnoxious. Does anyone know a fix for this? I tried searching for an answer, and tried unchecking "...switch to a space with open windows of that application" in System Prefences. But the problem persists, and I don't mind switching desktops when I click on an app I actually want to use.

You need to install Office on the computer from the installer DVD or disc image you purchased.

Will Microsoft Word ever work with OSX Lion?/Worth switching to iWork just for

I have the Microsoft Office Suite that I got with my computer, I want to know if it will work with an eventual Lion update before I consider updating to OSX Lion. I would like nothing more than to be able to update, but don't know if I'm willing to justify paying the 60 for iWork and then the 30 for LIon. Any suggestions either way would be great! I have been looking at the iWork package, but don't know how I feel about making the switch over...

Office 2008 and 2011 run under Lion, but Office 2004 and the Office 2008 installer don't.
(59590)

Microsoft Word crashing/lag time switching between apps

My Microsoft Word suddenly started crashing constantly. Everything is up to date with both Word and Mac software. Now, I'm starting to experience a lag between trying to highlight a word—same delay is happening when I go between applications. I have OS X and Word 2008. Thoughts?

I have the exact same issue. Whenever I switch to another app via the Dock, cmd-Tab, or clicking on another window, after a few seconds iPhoto crashes with no errors in the log (just a crash log). I had iPhoto Library Manager rebuild the library of 12,000 photos which took most of a day and had to restart through several crashes. The rebuilt library worked, but isn't really acceptable since it changed all the key photos on my events, lost all my facebook albums and slideshows, and seemed to ignore a few days of recent organizing and labeling.
It seems like some idle process (detecting faces maybe) is kicking in whenever iPhoto goes in the background that causes it to crash when it's backgrounded and idle.
The thread that crashed in the crash log is pretty uninformative:
Thread 15 Crashed:
0 com.apple.iPhoto 0x00423588 0x1000 + 4334984
1 com.apple.iPhoto 0x001bb71a 0x1000 + 1812250
2 com.apple.iPhoto 0x0005f909 0x1000 + 387337
3 com.apple.iPhoto 0x0005e133 0x1000 + 381235
4 com.apple.iPhoto 0x0001d80a 0x1000 + 116746
5 com.apple.iPhoto 0x00021cf5 0x1000 + 134389
6 com.apple.iPhoto 0x0001eb3b 0x1000 + 121659
7 com.apple.iPhoto 0x0001d8a9 0x1000 + 116905
8 com.apple.iPhoto 0x000235c1 0x1000 + 140737
9 com.apple.iPhoto 0x0003279c 0x1000 + 202652
10 com.apple.iPhoto 0x000348ff 0x1000 + 211199
11 com.apple.iPhoto 0x00035952 0x1000 + 215378
12 com.apple.iPhoto 0x000350c9 0x1000 + 213193
13 com.apple.iPhoto 0x00218882 0x1000 + 2193538
14 com.apple.Foundation 0x94941dfd -[NSThread main] + 45
15 com.apple.Foundation 0x949419a4 _NSThread__main_ + 308
16 libSystem.B.dylib 0x90035155 pthreadstart + 321
17 libSystem.B.dylib 0x90035012 thread_start + 34
I get no errors in the Console for iphoto when it crashes.
Any help would be appreciated on this painful issue.

Adobe does not recognize footers in Microsoft Word 2007 to PDF

I have copied and pasted the details, below, from a previous message I have sent out to an assistive technology listserv.
I am encountering this problem with various builds and versions of Adobe Acrobat:
Acrobat X on a Windows Vista 64-bit build (note that this is the best Acrobat I can install on Windows Vista, Adobe Reader XI is not even supported)
Acrobat X on a Windows XP build, sorry, do not know the bit count (it is my work computer so I can't upgrade anything)
Acrobat 9 on a Windows 7 64-bit build.
I have also encountered and checked into whether or not the PDF reads (and does what I want it to) in JAWS 14, latest update (Feb 2013). We encounter the same problem with JAWS and this morning found out that there is a conversion error between Word and Adobe. (See this post, where the ---- are).
Summary, I have spoken with JAWS, put out a support ticket with NVDA via e-mail, spoken with Microsoft, and tried to communicate with Adobe about this issue for help and Adobe is refusing to help. The other places tried everything they knew but they could not get it to work. I even tried to strip all the page numbers from Word and number using Adobe's page numbering feature, but that was not successful either because I cannot use Roman numerals.
I would appreciate any feedback the Adobe Forums can give me; please note that I cannot post a sample document at this time as the only document I have is a private work document (cannot share those by policy, so I will have to make up a fake document if I get the time and energy).
Thank you very much for your time and expertise. The pertient info is above and below in "Original Message" and "Activities section" - the other information is there if you'd like to look. And to provide feedback to Adobe about things I think they could improve, since they will not let me email them directly.
----Original Message----
My question concerns the reading of Footers / Headers in Microsoft Word 2007 and Adobe Acrobat (headers/footers designed in Microsoft Word 2007 and then converted to PDF with "Bookmark" checked in Adobe Acrobat conversion settings).
The document is a word document containing 50+ pages. There are 12 pages of "front matter" that are marked with Roman numerals. Subsequently, the body text of the document has an Arabic number (1, 2, 3, 4, etc.) in the bottom right corner. Footers are used properly in the document. All Table of Contents links, which do link to both headings in the "front matter" and to headings in the body text, are picked up properly. Literately, the only thing not reading on the document are page numbers (the Word Status bar is reading its page numbers, but the page numbers in the footer are not reading).
I then need to convert the document to Adobe Acrobat PDF. Granted, I have a full copy of Adobe Acrobat X available to me, and my various assistive technologies have always functioned better when opened directly in Acrobat (rather than Adobe Reader). So, I set the accessibility options (from Word) properly, asking it to bookmark Headers and Footers as appropriate, thinking that this will pick up the page numbers and make them read as the bottom right corner of my PDF.
All links work in Adobe to navigate by section/heading. All figures are alt tagged. Everything is perfect - but the one thing that NVDA won't read are the page numbers. Visually, the page numbers are there on the document, but NVDA won't pick them up. Additionally, I also changed the appropriate page numbers in Adobe (Page Thumbnail Pane, on the Navigation Pane I believe it is called) - to reflect the section where it is Roman numerals and Arabic numerals. This did not help, and for what it is worth, I cannot get NVDA to voice when I am in this pane, so I don't seem to have a chance of getting the page number info from there.
NVDA reads the document just fine except for the above-mentioned snare. However, when it reads, it will go to the next page, and say, "Page 2 of 54, (page text), Page 3 of 54 (page text)," etc. when I will need it to say Page ii of 54 (page text), Page iii of 54 (page text)," and so on, changing to "Page 1" when the Arabic numbers are used.
I know that the Page Label issue is part of Adobe's issue, with them not releasing the PageLabel aspect. (I have looked through some NVDA tickets). I do not know how to put a "changeset" into my copy of NVDA though, or even if it would help (I have no computer scripting skill). The easy answer would be to upgrade to Adobe Reader XI and see if that helps, but I don't have the ability to put it on every computer I use, and *I need this file to read consistently across multiple versions of Adobe* (including Adobe Reader/Acrobat 9, X, and XI). (This file is also going out to people who may not have the latest version of Adobe, but are also running some copy of NVDA, either a portable or a full install).
Is there any way to pick up the Footers with page numbers voicing in NVDA, and/or have it read the user-editable page number box that is on Adobe's Toolbar (next to the 1 of 54 parentheses). This user-editable box, to jump to page numbers, reflects the Roman numerals I have loaded into the pages of Adobe. When I press Ctrl+Shift+N in Adobe, I can also go to the appropriate page (if I type in iii, it will take me to iii, if I type in 34, it will take me to the Arabic number 34 -- NOT the 34 of 54, which would land me on a different page. And I want to land on the page that has the Arabic 34, so that's functioning fine.
I just need the page numbers in the footer to voice, "Page iii," or "Page iv," or "Page 29," etc. If I could get NVDA to do that, I could say to viewers of this document, "If you are using NVDA, remember to Ctrl+Shift+N to get the GoTo Box, then type in the page number you want if you cannot follow a link or a bookmark." This document is *very* accessible in my opinion with lots of ways to navigate...the only aspect of navigation that isn't being picked up are those footer page numbers!
I do have my Document Formatting settings on the NVDA menu set to "Report Headers," but that does not seem to help in either Microsoft Word 2007 or Adobe Acrobat. I have even switched the page numbers from the footer to the header to see if that would help and it didn't.
----Activities I have done today----
I spent over an hour on the phone today with Freedom Scientific (makers of JAWS) trying to troubleshoot this. We discovered that Footers will not read very well in JAWS and Microsoft Word 2007 (only solution is to stop reading document text and read Virtual Viewer text briefly, then go back out to document text, then back into Virtual Viewer which is NOT an acceptable or accessible solution whatsoever -- too much work for someone trying to read the document) -- and then we also discovered that:
Upon conversion from Word 2007 to .txt file (.docx to .txt), there are no alt tags for the figures in the document, or page numbers.
Upon conversion from Word 2007 to Adobe Acrobat X then to .txt file, every insert of a page number and footer is replaced with the same alt numberpad numerical code: the one that generates female. ♀No wonder JAWS and NVDA are skipping this, neither understand how to communicate it.
On the advice of JAWS Technical Support I contacted Microsoft Accessibility Technical Support and spent an hour on the phone with them. They say that unless Adobe can find a solution, it appears that it is impossible for Microsoft products to read the footer if JAWS was unsuccessful doing what I wanted it to do. The document/footer in question includes about 12 pages of front matter (numbered in Roman numerals) and 44 pages of body text (numbered in Arabic numerals).
I kindly explained to the Microsoft Support Agent that I found this issue hard to believe, although I understood. Sighted folks have the ability to make their documents look quite professional and that is the caliber and quality of documents anticipated from everyone, especially college students graduating from school, or job applicants. That a coding issue prevents the footer from being read properly, except in Edit view, is disappointing. The representative was with me 100% of the way. She completely understood where I came from. And yes, when I am designing the document myself, I know what I put there (or I pretty much do, anyway). But if I recieve a document, it is much harder to tell what is really there or not, or how the page numbers really lay. And this is confusing as heck, believe me.
I then called Adobe Technical Support, after having a brief online chat with them. Granted, I had to leave the chat in the middle because I got interuptted by something that was high-priority, but the woman chatting from Adobe says that chat is only for installation issues, and I will have to pay to open a support ticket. Excuse me? I have paid a hefty sum of money for Adobe Acrobat 9 and Adobe Acrobat X (work paid for the other Acrobat X copy). I deserve this problem to be troubleshooted for free. There was even a statement on the Adobe Acrobat X website that said Acrobat X users didn't have to pay for support, but Reader users did.
----Slight bit of rant and constructive criticism----
In speaking with Adobe Technical Support, I had to wait on hold for 30 minutes before my call was answered, and then I had to consent to being on hold countless times and had to answer, "Yes, I am converting from Word 2007 to PDF using Adobe Acrobat X" at least 6 times. The representative would put me on hold, then ask me the question, then put me on hold again, repeated 6 times over 45 minutes. At the end of 45 minutes (1 hour and 20 minutes of wasted time by now, that I must justify to my employer) - I told the representative I wanted to speak with his supervisor immediately, I did not care if he was trying to fill out a support ticket (and putting me on hold at least 4 more times in 10 minutes while he claimed he was filling out the support ticket) - and finally he put me on hold again and gave me to a very helpful supervisor. Within 6 minutes of speaking with the supervisor the supervisor had my support ticket filled out and I should recieve a call from Adobe within the next 30 minutes if his estimation was right (he estimated two hours, but it's been an hour and a half).
I have yet to know what can be done about my document. Freedom Scientific Technical Support is closed now for the day and I need to work tomorrow and Friday away from the phone. As I stated to Microsoft Accessibility Support, I truly feel that Adobe should read the page footers, every document says that Adobe should be able to read the page footers, and I feel slighted that as a person who uses assistive technology, there is some glitch that isn't making this happen. I am not blaming a specific place per se, except I am a little frustrated with Adobe especially since they have not gotten back to me, and I am frustrated with their customer service. JAWS customer service and Microsoft customer service were both exemparly, and I cannot say enough good things about them. My wasted time with Adobe however, that was disrespect in my opinion. And I certainly will not pay to open a support ticket, and my workplace has a site license. They've paid enough already.
If you've read this far, thank you. I look forward to replies, or at least understanding. And if anyone has ideas, I'd appreciate it very much (yes, I have tried taking the page numbers off and using Adobe's page number feature, but that would not allow Roman numerals. Only Arabic.).

Greetings NoNameGiven,
If I understand the problem correctly (I’m not sure I do) you would prefer ‘iii’ to be read as “eye eye eye” rather than “three”? The alt text property is the only way that I know of to make this happen. Hope this helps.
a ‘C’ student

I can't see the scrollbar on my microsoft word 2008 for mac documents

For some reason, in microsoft word 2008 for mac, I can't see my scrollbars on my documents. I've tried everything, but they aren't visible. This problem started when I got my new mac air and transferred over my programs and files. Any ideas?

make sure your documents setting on your iPhone is truned on for the iCloud. Go to settings, > iCloud > switch documents & data is on.

My Microsoft Word gives me an error report as soon as I try to open Word Document

I have the Microsoft Word for Mac 2011 and I've had it for almost 3 years now. I didn't have any problems until I decided to update it since I haven't done so when I installed Microsoft on my Macbook pro. After about 3 or 4 updates I started having difficulties when it suddenly gives me an error once I tried creating a new document that says: "Microsoft Word has encountered a problem and needs to close. We are sorry for the inconvenience." and underneath it says More Information so I clicked on it and this is what it gave me:
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2015-02-16 05:22:55 +0000
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 14.2.0.120402
Crashed Module Name: libobjc.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x000010a7
Blame Module Name: Microsoft Word
Blame Module Version: 14.2.0.120402
Blame Module Offset: 0x0021002b
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Crashed thread: 0
I clicked on check for updates just in case I missed any, but it says there's no updates available. Also, I restarted my computer twice and it still doesn't work. Did the updates messed it up? I really need to fix this problem soon because I'm going to need Word for school. Please and thank you!
Edit: I'll be moving this question over the other forum, but can anyone at least solve this problem for me here?

Microsoft Word is a Microsoft app. You should post your question to a Microsoft forum.
Cheers,
GB

File locking with OSX Server & Microsoft Word

We have a small office LAN based on a Airport Extreme bases station. Periodically Microsoft Word reports a break in connection to the shared folder where we store documents to get disconnected. When that happens and the user reconnects to the share, the user gets the file read-only message for the Word document that was open at the time.
I have found that in order to clear the read-only flag, I have to restart the server and open the Word file on the server with the ID of the user who was editing the file on the remote computer. Only that seems to clear the file locking that causes the file to be read-only.
I cannot figure out a less drastic way to release the lock file. I don't see any hidden temp files in the same folder as the document that is locked for editing found by ls -a or in the root direction of the shared folder in the .TemporaryItems/folders.<UID> that seems to be holding the lock.
I have run chflags nouchg <Word file> from Terminal, but that seems to have no effect either. I also used xattr to see if there were any locks held that way, but I don't see anything that way either.
File sharing to Macs only, which are configured just to use AFP through OSX Server.
Does anyone understand how the file locks of Word documents can be released directly with out restarting the server?
I should add that the underlying problems seems to be WiFi related. The behavior is that the WiFi connection seems to break long enough that the shared volumes disconnects. Outlook also causes a break. This behavior seems to have started with 10.9 and the purchase of new Retina Display MacBook Pros. I turned off AppNap on the Office applications but that is not clearly helpful. I also have been told the problem seems more likely to occur when Word is open in the background and another program like Outlook is in the foreground.
Any suggestions appreciated.

Apple write an operating system and also produce file sharing software as part of that to be used as a file server. Apple provide documentation for third-party software developers on how they should write software to work with Apple's software and also give those developers early access to new versions so those third-party developers can test and if needed make adjustments and issue updates to cope with any Apple changes.
Some third-party developers are good at dealing with this, some are bad, and some totally ignore what Apple does and give the impression they don't care if their product works properly or not. I think we can all judge where Microsoft sits.
It appears Microsoft have never paid any attention in particular to how Apple expect file-locking to be handled when accessing files on a Mac server. There have been problems for years and years and years with Office. Two other problems I have seen which seem different to yours but probably related are -
With Office documents it is supposed to be possible for more than one person to edit the same file at the same time, consider it a miracle if this actually works
With Office in particular Word, there is an auto-save function, unfortunately the way this seems to be implemented it seems that Word creates a new temporary file each time it auto-saves the document and keeps all the previous temporary files open still, this eventually means potentially over a hundred temporary files are open - just for one Word document and you can then hit a limit on the total number of files you are allowed to have open at the same time. At this point further auto-saves fail, and you also encounter great difficulty doing a real full save of the document.
I do not hold Apple completely blameless over this issue, it is likely their file-locking implementations change too often, and have inadequate documentation, however even considering this a company the size of Microsoft with the amount of sales (and profit) they derive from Office for the Mac has no excuses at all for failing to put the effort in to resolve any such clearly critical problems.
We could go on and on about other areas where Microsoft don't play by the (software) rules. Even in Windows Office does not obey the standard print dialog rules Microsoft specified themselves!
Unfortunately not only is Office for Mac upgraded infrequently, but even when new paid for upgrades are released Microsoft have a history of still not fixing bugs. It goes without saying that a mere free update is even less likely to actually fix a bug, typically such free updates only address security issues. The next version of Office is going to be Office for Mac 2014 see http://www.macworld.com/article/2106643/microsoft-will-release-a-new-version-of- office-for-mac-this-year.html
One area I confidently predict Microsoft not to resolve in Office for Mac 2014 is that fact that Word for Mac still does not support right-to-left languages like Hebrew and Arabic. This is despite the fact that OS X itself has supported this for years and years, and despite the fact other Mac programs support this including the free TextEdit and Pages - both of which can read Word files. Some people may remember that at one point the Israeli Government temporarily banned all Microsoft software over this issue. See http://apple-beta.slashdot.org/story/03/10/15/2215249/israeli-government-suspend s-microsoft-contracts This issue goes back over TEN years!!
I note that Microsoft has now taken their OfficeForMac blog offline, probably due to the weight of criticisms. I would not say it is due to out-right anti-Microsoft hate, that war ended long ago. We just want products that work. I myself do use Microsoft products, even at home - where they are the best solution, so I use Microsoft Media Center for example. Sadly this is now being neglected by Microsoft.

Microsoft Word Freezing Repeatedly, Application Not Responding

Just wondering if anyone else was having issues with Microsoft Word from MS Office 2008, where you open the application, you type a few sentences, and the application freezes with the spinning circle of death that won't go away until you click the dock where it says "application not responding" and do a force-quit? You can leave the circle spinning for 10-20-30 minutes, and it never goes away.
Now for the weird part--this error only happens for me when I'm using a specific document on my computer. I can open Word, start a new document, type several paragraphs of text, and it works fine. But I've been working on an existing paper for about two months that all of a sudden started causing these freezes/crashes when editing it. It's about 30 pages roughly, no images, no big inserts that would take up a lot of memory (116 kb in size). And up until today, there were no problems. So why all of a sudden can't I edit anything on this paper without freezing the program?! I downloaded the Microsoft Office 2008 Service Pack 1 that was just released after this problem started, and ran all the recent Java and program updates through Software Update with computer restarts. I even copied the text from the Word document I was working on, pasted it into a new document, tried saving it as both .doc and .docx, and again the program still freezes when working with that text in a new file. This one baffles me. It's like the text within a document is somehow freezing the application. One thing I did notice is that the freezes seem to happen when I'm scrolling using a mouse wheel. Not always, but quite a bit. I suppose this is some memory issue related to several pages of text that the program can't render or process when you add new lines of text or scroll, but again, I can't figure why this paper I've been working on for months all of a sudden decided to start freezing Word today. Can you really only have 30 double-spaced pages of text in Word before it crashes?
Looks like I've found my reason to switch to Open Office, since I'm 3-4 days out from a deadline. Any other solution strategies would be welcome. Thanks.

Same problem here - Microsoft Word 2008 (update 12.1.7) will open fine, and then start the spinning pizza of death. Only way out is to force-quit the app. I've tried:
1) deleting plist and font cache files
2) uninstalling MS Office 2008, reinstalling and then re-applying updates 12.1.0 and 12.1.7
3) confirming that Apple's Font Card.app can verify all fonts
No luck. Currently I can't open any MS word doc without the spinning pizza of death.
If you are lucky enough that these symptoms only happen with a specific Word .doc file, I would see if the PC-originator could re-save the file as .RTF and resend. If you can then open it OK, you could revert back to .doc (or .docx) format. RTF format is Microsoft's interchange format. If there are anomalies in the .doc file, saving as .RTF can sometimes clean them up. Once done, you can revert back to native MS Word format.
...b

How can I change a Microsoft Word document file into a picture file?

How can I change a Microsoft Word document file into a picture or jpeg file? I am wanting to make the image I created my background on my macbook pro.

After I had the document image the way I wanted it, I saved it as a web page and went from there. Below are the steps starting after I did the "save as" option in Word:
1) Select "Save As Web Page". I changed the location from documents to pictures when the window came up to save it as a web page.
2) Go to "Finder" on you main screen, or if it's on your main toolbar at the bottom.
3) Click on the "Pictures" tab and find the file you just re-saved as a web page. (I included "web page" or something similar in the new title so I could easily find the correct file I was looking for)
4) Open the correct file and then "right click" on the actual image. (Use 2 fingers to do so on a Mac)
5) Select 'Use Image As Desktop Picture", and voilà! The personally created image, or whatever it is that you wanted, is now your background.
**One problem I encountered while doing this is that the image would show up like it was right-aligned in relation to the whole screen. The only way I could figure how to fix this was to go back to the very original document in Word, (the one before it was saved as a web page), and move everything over to the left.
I hope this helps someone else who was as frustrated as I was with something that I thought would have been very simple to do! If you have any tips or suggestions of your own, please feel free to share. : )

I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word"

I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word".I am sure that document is not corrupted and
all. something it showing the preview and sometimes it throwing this error. I hope this error is intermident. When clicking on the link also it throws this error but on refreshing it working fine. I dont know why it is happening. Please helpme to resolve
this issue.

Hi Waqas
Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
Issue #3 in the above blog link does not reflect the same error I see on my servers.
I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
If you added domains to the Allow List by using the
New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
New-OfficeWebAppsHost cmdlet.
I have not added any domains to the Allow list so this did not help either. Should I add the domain?
Any further help with this is much appreciated.
Thanks again.
Yoshi

Network home folders, collaboration sharepoint and Microsoft Word 2008

I'm hoping someone who knows how Microsoft Word 2008 works on network volumes can shed some light on our situation.
We run a small managed network with about 15 leopard clients and a leopard server. We've got two sharepoints, a "homes" share for network home folders, and an "Office" share with our shared office document folders.
Several times a week, users will encounter a situation where Microsoft Word 2008 will claim that a file is open by another user, or that the file can be opened in "read only" mode, even though the file is not in use. Naturally, the problem cannot be replicated when I am present.
### My Hypothesis ###
My users are in the habit of quickly borrowing machines from other users to pull up documents in the "office" share by using the "connect as" button. So, for example, userA is logged in to her machine (and is thus connected to the network home folder on the server). userB comes along and borrows her machine -- without logging out, will connect to the shared office folder, pull up and edit/print a document, etc. We're not currently auto mounting the office share.
I know that Microsoft Word creates lock folders located in the .TemporaryItems folder at the root level of the "office" share. The folders are named "folder.xxxx", where xxxx is the userid of the account that created the lock folder. Everyone uses a network account, so everyone has a unique userID. If I list the .TemporaryItems folder using the CLI, i can see lock folders that are several days or a week old. So Word doesn't seem to be cleaning up after itself immediately, at least not always.
So my question: when userB connects to the office share on a borrowed machine (logged in to the client machine using the network home folder of userA), is it possible that word will now create lock folders for userB, and will be unable to clean up lock folders created by userA?
Anyone have other ideas for investigating the "file in use" problem?

Switched user back to the network home folder and adjusted the MS Word preferences so that the autorecovery files would be stored on the local client machine. There doesn't seem to be a comparable setting in the Excel preferences.
My initial testing suggests that this has reduced how often this problem occurs, but has not eliminated it. I tested by repeatedly opening and closing a couple of different word files in rapid succession -- i was able to replicate the "file opens as read only" problem occasionally.
I've talked to Apple server support about this issue. While they were helpful, they didn't have an explanation or solution for this problem. There are a number of postings in the microsoft mactopia discussion boards site where people report similar problems.

Microsoft word switch over

Similar Messages

Maybe you are looking for