• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 502
  • Last Modified:

Cannot edit word with excel embedded object

Hi all, I have a client that is unable to edit a word document that has an excel object embedded in it. He has office 2010. He gets these files all the time, he is able to open the ones from last year. The ones from last year have a .doc extension. The ones this year have .docx. Tried changing the extension to .doc, still no luck. He sent me the file, and I am unable to edit the file either. I have disabled all com addins, still no luck. I am not able to convert the object to anything else either. if I copy the object and paste it into another word document, it works. That is not an option cause there are too many of them to have to copy. Screenshot of error message is attached. I have been all over the net, no luck, so I am here seeking your help. I tried changing protected view options, unchecked and checked Ignore DDE, still nothing. Not sure why he is able to still edit the old ones and not these new ones. Heck, as I mentioned, I am not able to edit them either. My co-worker is able to edit it
  • 3
  • 3
2 Solutions
Changing the extension is merely claiming the file is a different format. In fact the structure of the data inside the 2 file formats is completely different - you can't just change a docx to a doc by changing the file extension.

You can however use Word to save to different formats. If you open the docx in Word and use save as it will write the data out in the other format.

- Have you tried opening the docx and using save as doc?
- Does your client have matching versions of Word and Excel?
Another idea. When you disabled all COM add-ins did you do it in Word or Excel? I think Excel is the critical part!

Maybe try opening a blank excel, disable all COM add-ins then close and try opening the doc again.
Stacy BrownSenior Applications AdministratorCommented:
We've seen this error in the office.  We had to open Excel, open Word, open the file from within Word in order to work on them.

I don't know if this will work for you, but that's how we worked around the error.
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

xzay1967Author Commented:
Thanks for all the responses.
He has matching versions of word and excel. There is only one suite installed, 2010.
I have tried saving as a doc, and it yielded the same error.
Oddly even though I went this route before, but I disabled the com add-ins and was able to get it to work Here is what I observed:
Opened word doc, double clicked on embedded object, error appears. Launched Task Manager, excel is running in background (as it should). Even more odd, is that the com add- in in question, had always been there when he was able to edit the files in the past year. The only real difference with the files he is getting this year is that they are .docx vs .doc. While he is able to use the file with the com add-in disabled, I would prefer a more permanent solution. The com add-in is mandatory for him to have. Luckily working with this type of file is not an every day function. The add-in is called F9, and he uses it to connect to some source to do his financial number crunching in excel. I showed him how to enable and disable it as his needs dictates. He is ok with that.....for now.
Theory 1

I'm assuming if you just open Word that when you need to edit the object it fires up Excel which starts loading add-ins and the add-in is just taking too long to do something.

Did you try this sequence?
- Open Excel
- Open Word
- Open document
- Try to edit embedded object

Perhaps this allows the add-in to load in advance.

Theory 2

I guess the another possibility is that the add-in tries to do something each time an excel sheet is loaded. Your embedded object is probably like any other worksheet to excel, just not displayed through the Excel UI.

Perhaps the new Word exchanges data with Excel in a slightly different (richer?) way which has pushed this processing step over some timeout limit? The old docs would still work because they don't possess the richer data in the documents.

If this is the case I don't think you have much option - the add-in manufacturer would need to optimise their code.
xzay1967Author Commented:
This is still an issue, and so far the only workaround is for me to disable the add-on fir him whenever he needs to work with that file. At this point the moderator can delete this question, but I do appreciate the efforts of everyone.
xzay1967Author Commented:
Upgrading to the latest version fixed the issue..well temporarily. Once we applied SP2 to office, it broke it again lol.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now