Microsoft word 2008 slow save with iMac 2009 and yosemite

I have microsoft word running on 4 different iMacs, all using Yosemite. My 2008 iMac 2009 iMac and 2014 retina display iMac all save word docs quickly. My 2011 iMac saves word docx and word doc documents slowly. All machines are basically the same. Memory is not the issue. I am running same updated version of word 2008 in same configuration. I reinstalled word on 2011 slow save iMac to no avail. problem started after upgraded to yosemite. i have 12 gigs of ram as i thought ram was issue. Any thoughts welcome. Are others noticing same problem?

There has been a better and free alternative to old versions of MS Word and MS Office since forever. Apache OpenOffice 4.1.1 is the latest version of a free and complete All-In-One document processor, spreadsheet, drawing, presentation, database, & formula software, found here: http://www.openoffice.org
It also reads, writes and translates MS Word, saves in many formats, and is pretty easy to use. It's entirely modern and compatible with all the latest Mac operating systems. Good luck.

Similar Messages

Microsoft Word 2008 keeps crashing with Mountain Lion 10.8.3.

I've had this problem off and on, and judging from the forums, it seems to be common. Following advise on one discussion forum and a visit to the genius bar, I tried deleting the .plist files in the preferences folder for Word (following advice found here: http://support.microsoft.com/kb/948489). This worked for a bit, but now the problem is back. I can't type two words before Word crashes. Does anyone have a solution?
The following error message appears after the crash:
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2013-04-02 00:45:55 +0000
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: unknown
Crashed Module Version: unknown
Crashed Module Offset: unknown
Blame Module Name: unknown
Blame Module Version: unknown
Blame Module Offset: unknown
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Thread 0 crashed:
# 1 0x9a492843 in ( + 0x00000000)
# 2 0x9a494dbc in ( + 0x00000000)
# 3 0x18739607 in ( + 0x00000000)
# 4 0x1873968d in ( + 0x00000000)
# 5 0x18757bbe in ( + 0x00000000)
# 6 0x187b134d in ( + 0x00000000)
# 7 0x187b7d82 in ( + 0x00000000)
# 8 0x015dae76 in ( + 0x00000000)
# 9 0x015daee0 in ( + 0x00000000)
# 10 0x015dbc2d in ( + 0x00000000)
# 11 0x00617d3a in ( + 0x00000000)
# 12 0x0061cb21 in ( + 0x00000000)
# 13 0x0061ceaf in ( + 0x00000000)
# 14 0x008b5410 in ( + 0x00000000)
# 15 0x00623565 in ( + 0x00000000)
# 16 0x006264a1 in ( + 0x00000000)
# 17 0x008b7dc4 in ( + 0x00000000)
# 18 0x008b7e94 in ( + 0x00000000)
# 19 0x000038fc in ( + 0x00000000)
# 20 0x000039fd in ( + 0x00000000)
# 21 0x00c57163 in ( + 0x00000000)
# 22 0x01621afe in ( + 0x00000000)
# 23 0x9a052c81 in ( + 0x00000000)
# 24 0x936f7416 in ( + 0x00000000)
# 25 0x936f6db5 in ( + 0x00000000)
# 26 0x936dbbc2 in ( + 0x00000000)
# 27 0x936db02a in ( + 0x00000000)
# 28 0x936dae9b in + 0x0000E7F0 ( + 0x00000000)
# 29 0x9a03cf5a in ( + 0x00000000)
# 30 0x9a03ccc9 in ( + 0x00000000)
# 31 0x9a1a215c in ( + 0x00000000)
# 32 0x01661ce4 in ( + 0x00000000)
# 33 0x00ae3e6b in ( + 0x00000000)
# 34 0x00aecd18 in ( + 0x00000000)
# 35 0x02236080 in ( + 0x00000000)
# 36 0x00ad2438 in ( + 0x00000000)
# 37 0x000028e2 in ( + 0x00000000)
# 38 0x00002809 in ( + 0x00000000)
X86 Thread State:
eax: 0xacd99a28 ebx: 0xffffffff ecx: 0x9a457947 edx:0xffffffff
edi: 0xffffffff esi: 0xacd99a28 ebp: 0xbfffda28 esp:0xbfffda10
ss: 0x00000023 eip: 0x9a492843   cs: 0x0000001b   ds:0x00000023
es: 0x00000023   fs: 0x00000000   gs: 0x0000000f eflags:0x00010282
Thread 1:
# 1 0x928b69ae in ( + 0x00000000)
# 2 0x9354b7a9 in ( + 0x00000000)
X86 Thread State:
eax: 0x0000016b ebx: 0xb0102700 ecx: 0xb01025ac edx:0x928b69ae
edi: 0x00000000 esi: 0x9354b8a1 ebp: 0xb0102718 esp:0xb01025ac
ss: 0x00000023 eip: 0x928b69ae   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000246
Thread 2:
# 1 0x928b60ee in ( + 0x00000000)
# 2 0x9a431e79 in ( + 0x00000000)
# 3 0x9a419d2a in ( + 0x00000000)
X86 Thread State:
eax: 0x00100170 ebx: 0x9a431cc7 ecx: 0xb0184f6c edx:0x928b60ee
edi: 0xb0185000 esi: 0xb0185000 ebp: 0xb0184f88 esp:0xb0184f6c
ss: 0x00000023 eip: 0x928b60ee   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000282
Thread 3:
# 1 0x928b38e6 in ( + 0x00000000)
# 2 0x9a4c06b6 in ( + 0x00000000)
# 3 0x01aa4265 in ( + 0x00000000)
# 4 0x01aa38cd in ( + 0x00000000)
# 5 0x01aa3954 in ( + 0x00000000)
# 6 0x01aa440d in ( + 0x00000000)
# 7 0x9a42f5b7 in ( + 0x00000000)
# 8 0x9a419d4e in ( + 0x00000000)
X86 Thread State:
eax: 0xffffffa6 ebx: 0x00000000 ecx: 0xb0206a9c edx:0x928b38e6
edi: 0x00005ce0 esi: 0xc811fc9c ebp: 0xb0206ae8 esp:0xb0206a9c
ss: 0x00000023 eip: 0x928b38e6   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000246
Thread 4:
# 1 0x928b60ee in ( + 0x00000000)
# 2 0x9a431e79 in ( + 0x00000000)
# 3 0x9a419d2a in ( + 0x00000000)
X86 Thread State:
eax: 0x00100170 ebx: 0x9a431cc7 ecx: 0xb0288f6c edx:0x928b60ee
edi: 0xb0289000 esi: 0xb0289000 ebp: 0xb0288f88 esp:0xb0288f6c
ss: 0x00000023 eip: 0x928b60ee   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000282
Thread 5:
# 1 0x928b4eb6 in ( + 0x00000000)
# 2 0x016e7552 in ( + 0x00000000)
# 3 0x015f58b8 in ( + 0x00000000)
# 4 0x9665ea7b in ( + 0x00000000)
# 5 0x9a42f5b7 in ( + 0x00000000)
# 6 0x9a419d4e in ( + 0x00000000)
X86 Thread State:
eax: 0x000c0194 ebx: 0x015f5867 ecx: 0xb030ad5c edx:0x928b4eb6
edi: 0x928b3e77 esi: 0xb030af44 ebp: 0xb030ad78 esp:0xb030ad5c
ss: 0x00000023 eip: 0x928b4eb6   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000286
Thread 6:
# 1 0x928b3826 in ( + 0x00000000)
# 2 0x015f5c7b in ( + 0x00000000)
# 3 0x9665ea7b in ( + 0x00000000)
# 4 0x9a42f5b7 in ( + 0x00000000)
# 5 0x9a419d4e in ( + 0x00000000)
X86 Thread State:
eax: 0xffffffda ebx: 0x015f5a95 ecx: 0xb040ee7c edx:0x928b3826
edi: 0xb040ef56 esi: 0xb040eed4 ebp: 0xb040eea8 esp:0xb040ee7c
ss: 0x00000023 eip: 0x928b3826   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000206
Thread 7:
# 1 0x928b60ee in ( + 0x00000000)
# 2 0x9a431e79 in ( + 0x00000000)
# 3 0x9a419d2a in ( + 0x00000000)
X86 Thread State:
eax: 0x00100170 ebx: 0x9a431cc7 ecx: 0xb038cf6c edx:0x928b60ee
edi: 0xb038d000 esi: 0xb038d000 ebp: 0xb038cf88 esp:0xb038cf6c
ss: 0x00000023 eip: 0x928b60ee   cs: 0x0000000b   ds:0x00000023
es: 0x00000023   fs: 0x00000023   gs: 0x0000000f eflags:0x00000282
Loaded modules:
Operating System Information
Operating System: Mac OS X 10.8.3 (Build 12D78)
CPU: Intel Core Duo, Number: 4, Speed: 2147 MHz
gestaltPhysicalRAMSize err = 0, result = 2047 MB
gestaltSystemVersion err = 0, result = 0x1083
Screen: 1280 x 800, depth = 32, ltbr = 0, 0, 800, 1280
Microsoft Application Information:
Error Reporting UUID: 9D8D8CC4-51B1-4B80-A492-9A39F90897AA
Time from launch: 0 hours, 0 minutes, 38 seconds
Total errors on this client: 87

Post your question on Microsoft's Mac forums since it's their software you're having issues with: http://answers.microsoft.com/en-us/mac

Yosemite compatibility with microsoft word 2008

I had held off on upgrading to Mavericks because of the issues surrounding the compatibility with Microsoft Word 2008. I am a student and need to use Word to do my work as well as having all of my current documents, including my thesis, in 2008 format. I don't want to risk losing the information or the ability to do my work and I was wondering if there is any information about whether the issue of compatibility with this version had been fixed. I don't have the means to buy a new version of Microsoft but would very much like to be able to update my system since I am still using Mountain Lion.

There has been a better and free alternative to old versions of MS Word and MS Office since forever. Apache OpenOffice 4.1.1 is the latest version of a free and complete All-In-One document processor, spreadsheet, drawing, presentation, database, & formula software, found here: http://www.openoffice.org
It also reads, writes and translates MS Word, saves in many formats, and is pretty easy to use. It's entirely modern and compatible with all the latest Mac operating systems. Good luck.

Cannot Interact with Microsoft Word 2008 for Mac after Opening

After I open Microsoft Word 2008 for Mac, either by opening a .docx file or opening Word from the Applications folder, I am not able to interact with the application whatsoever. Selecting its icon in the dock does not bring any of its windows to the front, nor does it show the Word menu at the top; instead, it still shows the menu of whatever application was previously selected. But the windows do exist if I move other windows out of the way. If I do get to a Word window, I cannot click on anything, select anything, resize it, close it, or scroll.
Other info: If I click and hold the Word icon in the doc, the menu displays as if the application were functioning normally; it does not show a Force Quit option, as it would if Word were frozen. I do not see any dialogue boxes or anything that would take the focus away from the other windows.
Background: I was able to successfully use Word without any problems before today, using the same installation of the application, same computer, and same operating system. I also never had this problem before Mavericks, though, as I said before, I didn't always have this problem in Mavericks.
How do I get Word to function normally again? Thanks for any help you can provide!

After letting Word run for quite a while, a popup window told me there was an issue with the database. I opened the Microsoft Database Utility and rebuilt the database. It seems to be working fine now.

Microsoft Word 2008. 12.7.6 compatible with Mountain Lion

My I Mac is 2- 3 years old. It has 10.6.8. and I would like to upgrade to Mountain Lion (mainly in order to process Raw photo files for a new camera I bought).
So far so good.
However, I want to know if I upgrade can I still use my Microsoft Word (2008). 12.3.6 without any glitches. I hate glitches !!!
I am not tech savy so I would so much appreciate simple answers to these complex problems.
I very much appreciate your advice. Thank you.
Perplexed. Don

Yes.

Microsoft Word 2008 Error Message-Wont Open?

Hello,
I have a 2009 MacBook Pro, operating system OS C 10.6.8, I updated to Snow Leopard about a year ago. I tried to open my Microsoft Word (2008), and receive "Microsoft Word has encountered a problem and needs to close." With the options of Send/Don't Send and to try and reopen. It will not open. I have tried to repair the disk permissions using Disk Utility, I have also tried to Remove Duplicate Fonts as I read this may be a problem. I do not have any software updates, and I have tried restarting multiple times. Can anyone offer me some help on this issue, I don't know if I still have the disk to reinstall Microsoft OFfice.
Thank you!

Also, the error message says this:
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2013-12-01 14:41:57 -0600
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.3.6.130206
Crashed Module Name: Microsoft Word
Crashed Module Version: 12.3.6.130206
Crashed Module Offset: 0x00152a74
Blame Module Name: Microsoft Word
Blame Module Version: 12.3.6.130206
Blame Module Offset: 0x00152a74
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Crashed thread: 0

Word 2008 doc saves into multiple docs instead of one PDF

I have installed Acrobat 9 Pro and am trying to print a Word 2008 doc to a PDF. Instead of creating and saving as one document it splits it into several whenever the page set up changes from profile to landsacape or vice versa. This happens whether I use the PDF print button or the Adobe Printer option. Any advice would be gratefully appreciated. Cheers.

I am afraid to break the news to you, this has been an on going problem with Acrobat converting Word File to PDF. Its been a problem from the get go. Adobe says, its Microsoft's Problem. Microsoft says its Adobe Problem, they both blame Apple. Problem, is Apple licenses the PDF subsystem used OSX since day one from Adobe; and, the problem existed in OS9 which didn't use PDF as the the underlying print/display engine, which tends to point the finger to Adobe. Another thing point to its adobe's problem, is that Microsoft has been waiting patiently for adobe to fix the problem since day one about 10-15 years, So they desided in Office 2008 to use their own built in Converter for PDF. This reduces the problem of breaking the pdf up only if you have a shift orientation. The problem lies in Adobe either doesn't know how or can't figure out how, or doesn't want to be bothered with finding out how microsoft Page and Section breaks work. They are unique to Microsoft.
The cure is to either use Word 2008's Save as... Command then choose PDF. In which case unless you have a chart or something that should be in Landscape mode, will make a complete PDF.
Or to take the pieces that are created by Acrobat/Distiller AdobePDF Print Drive and doe the following:
Open the first part, scroll to end
Then go to Edit menu and choose Edit menu > Insert Pages
Locate second part and choose okay or insert.
repeat 1-3 with next section
Continue doing this until all the pieces are together.
There is no way around this problem other than not using page and section breaks and not using charts or items that require viewing in Landscape orientation. Which may or may not be realistic.
If you must use items in landscape mode my suggestion would be create them separately and, then when printing, print them speparately one copy, then place the chart where you want and use a Copy machine to make the copies in the right order. Or use my direction above to insert them in proper place.

Mac Microsoft Word 2008 double side printing

Hi.
I recently purchased Macbook Pro 15, and installed Microsoft Office 2008.
I have a SamSung Express 282 series laser printer.
When I use my window pc or window labtop, it double-side prints all right.
But when I try to double-side print with Mac Pro Microsoft word 2008, it doesn't work.
From the Print menu, I go to 'printer feature' and click on 'reverse two-sided printing', but it keeps saying
"Changing the setting of Reverse Two-Sided Printing to On would cause a conflict that cannot be resolved. No change will be made,"
and does not let me click on it.
Does anyone know what's going on?
I really want to save some trees and do only double-sided printing, but it doesn't let me.
Any help would be greatly appreciated.
Thanks, guys.

http://www.usa.canon.com/cusa/support/consumer/printers_multifunction/pixma_ip_s eries/pixma_ip4200#DriversAndSoftware
Be sure to pick the OS X Lion 10.7 driver from the pulldown menu before selecting the driver category below it.
If that doesn't work, contact Canon. There are some Lion supporting double sided printers for sure.
Mind you,when manufacturers rely on the CUPS drivers as they did in this instance they may have
taken the easy way out, and that might avoid having the double sided printing.
http://support.apple.com/kb/dl899 may be able to patch those drivers to give you double sided printing if the Canon ones do not.
There are a few other open source alternatives*.
When double sided printing doesn't work, the trick is to rotate the pages upside down and feed face down switching odd and even page numbers.
Test with single sheets first, and then once you get the hang of it, do multiple.
I don't know where your printer feeds, so you'll have to try a couple times to figure out the correct direction.

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 2008 crashes abruptly when trying to use track changes

Hi,
I believe this may be related to recently downloading Yosemite:
Every time I try to use Microsoft Word (2008) with "track changes" on, Word shuts off abruptly.
Has any one else had this problem? Is there a way to fix it?
I've already tried Disk Utility - disk & disk permissions repair.
Help would be greatly appreciated.
Thanks.

You should note that this forum is for troubleshooting Apple Software Update for Windows, a software package for Windows designed to update Apple products that run on Windows, and not related to Microsoft Office or your question in any way. If you have issues or questions about Office, it's probably best you post Office related questions on Microsoft's own forums for their Mac products.
http://www.officeformac.com/productforums

Microsoft Word 2008 top menu bar changed to chinese - ISSUE

After opening a MSfile the Leopard top menu when using Microsoft Word 2008 has been changed to Chinesse. This issue only happen with this product and not with the rest of the Microsoft tools that I have installed in my MacBook (example: Powerpoint). I'm including a print screen (as you can see only the iOS menu is changed to chinesse and not the software menu). I extremely need to change it back to English!
Thanks for any information and advice that you could provide

Never heard of something like that. AFAIK, Office 2008 distributions do not contain localisation resources, so there would be no way for (US) Word to display menus in Chinese. Maybe you have a multi-lingual version? Check what's available in the Microsoft Language Register, although I was under the impression that it did not affect menu display. And… are you sure it's Word 2008 and not 2011?
Btw, an unrelated issue. Did you recently open a Word doc having to do with Tibet?

Microsoft Word 2008 does not work after lion installation

After I installed Lion in my MacBook Pro, Microsoft word 2008 failed to work properly. Each time I try to quit word an error message appears and word closes and reloads automatically. The only way I can now really quite word is by the 'Force quit' option (in the apple menu). Word was working properly with Snow Leopard, so no idea what happened there... Any hint? Thanks

Ok, did exactly what you said... To 'make word crash' I only had to open it and then try to 'quit' it, in crashes 100% of the time...
1/3/12 11:43:29.066 AM com.apple.launchd.peruser.501: ([0x0-0x99099].com.microsoft.Word[970]) Exited: Killed: 9
1/3/12 11:43:31.983 AM Microsoft Error Reporting: CFURLCreateWithString was passed this invalid URL string: '/StageOne/Generic/MacCrash/com_microsoft_word/12_3_2_111121/microsoftcomponent plugin/12_3_2_111121/0x000ed279.htm?lcid=1033&os=10.7.2&testDrive=NO' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
1/3/12 11:43:31.984 AM Microsoft Error Reporting: CFURLCreateWithBytes was passed these invalid URLBytes: '/StageOne/Generic/MacCrash/com_microsoft_word/12_3_2_111121/microsoftcomponent plugin/12_3_2_111121/0x000ed279.htm?lcid=1033&os=10.7.2&testDrive=NO' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.
1/3/12 11:43:31.984 AM [0x0-0x99099].com.microsoft.Word: 2012-01-03 11:43:31.983 Microsoft Error Reporting[977:7703] CFURLCreateWithString was passed this invalid URL string: '/StageOne/Generic/MacCrash/com_microsoft_word/12_3_2_111121/microsoftcomponent plugin/12_3_2_111121/0x000ed279.htm?lcid=1033&os=10.7.2&testDrive=NO' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateWithFileSystemPath or CFURLCreateWithFileSystemPathRelativeToBase should be used instead.
1/3/12 11:43:31.984 AM [0x0-0x99099].com.microsoft.Word: 2012-01-03 11:43:31.983 Microsoft Error Reporting[977:7703] CFURLCreateWithBytes was passed these invalid URLBytes: '/StageOne/Generic/MacCrash/com_microsoft_word/12_3_2_111121/microsoftcomponent plugin/12_3_2_111121/0x000ed279.htm?lcid=1033&os=10.7.2&testDrive=NO' (a file system path instead of an URL string). The URL created will not work with most file URL functions. CFURLCreateFromFileSystemRepresentation should be used instead.
I hope you can make some sense of all that!
Thanks!

Pasting text that was copied from microsoft word 2008

In dreamweaver CS3, if I want to paste text that I have
copied from Microsoft Word 2008, i have to paste it in entourage,
copy that and THEN I can paste in dreamweaver. I can't paste
directly in Dreamweaver from word. is there an extension that will
cut out this extra step?
Thanks much,
Page

I just copied two paragraphs of text from Word 2008, and
pasted it into DW's
Design view. No tables.
What is it you are copying?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"micdim1" <[email protected]> wrote in
message
news:glaf2g$m11$[email protected]..
> DW CS3 does not work with Word 2008. Problems with
pasting.
>
> Adobe says that DW CS4 works with Word 2008, however
when I have pasted
> from
> Word 2008 into DW CS4, the text gets inserted into a
Table. This happens
> with
> all options except for "Text Only" option.
>
> The work around for DW CS4 is to either open up a Word
document with
> TextEdit
> and copy/paste from there, or paste the Word text into
DW, copy the text
> again
> from DW (which is inside a table now), delete the table
with the text, and
> then
> paste the text again.
>
> If anyone knows of another solution please let us know.
>
>
>
>
>

I can't type in my Microsoft Word 2008 anymore on MacbookPro, how do I fix this?

I have a MacbookPro from 2009 and my Microsoft Word 2008 won't let me type or use any keyboard functions on the page. I still have full use of my mouse/cursor. I also just recently updated to Yosemite. Help!

This just started happening to me, too, about an hour ago. I updated My Macbook Air 2013 to Yosemite a day after it came out, and I use Microsoft Word 2008 quite frequently (several hours a day), yet this just started happening.
TEMPORARY SOLUTION: I find that if I completely quit Microsoft Word and reopen it, I am once again able to type.
It's happened to me twice so far tonight. This second time I noticed that it was right after I copy and pasted something, then changed it to double space. Have you noticed anything similar?

Microsoft word doesn't work with Yosemite. Please Help

Microsoft word doesn't work with Yosemite. Please Help

Office 2008 and 2011 work with Yosemite. If you had Office 2004 installed, then it will not work. If you had Office 2008 I would upgrade to Office 2011. In any event you should try completely uninstalling Office and then reinstalling it.

Microsoft word 2008 slow save with iMac 2009 and yosemite

Similar Messages

Maybe you are looking for