The original document is in Word 2007 and the embedded document is also in
Word 2007. A work around is to convert the embedded document into Word 2003
but when multiple (50-100) documents come through it takes too much time and
he must forward these out when he is finished with them. This being said, I
can convert the files to 2003 with no problem but if I try to convert back to
2007 I receive an error stating "Word cannot start the converter mswrd632",
even though I just used the converter. Luckily working the documents in 2003
isn't an issue.
I've read that this can be a problem when Office 2003 SP 3 is installed but
that is not installed. Office 2003 Resource Kit is installed.
The computer in question is:
Dell Optiplex 745
3.25 GB Mem
XP Pro SP2
Office 2007 Pro+ 2007
Thanks,
Michael
If the Applet for WordPad does not exist, create it and set its value to 1.
Alternatively, Restore your computer to a restore point created about 3
weeks ago before this problem started to crop up.
--
Hope this helps.
Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.
Doug Robbins - Word MVP, originally posted via msnews.microsoft.com
"Michael E. SLoan" <Michael E. SL...@discussions.microsoft.com> wrote in
message news:33D731DC-2691-4486...@microsoft.com...
I followed the instructions and unregistered the converter and I still
received the error “The program used to create this object is word. That
program is not installed on your computer. To edit this object, you must
install a program that can open the object.”
I then put the registry key back (I exported it before deleting it) and then
re-enabled the converted by adding the AllowConversion registry entry but I
still receive the same error.
If I drag and drop the embedded file onto my desktop it creates a scrap file
that does open in word so I’m still foggy as to why it won’t open directly
from the original email attachment.
I'm still looking for a solution to this problem (please see original post)
and for now I'm having everyone embed their docs into docs using Word 03.
It's working better than Word 07 but the problem seems to be spreading. Now
I have multiple customers with the same problems on both the Dell Optiplex
and on Trusted Thin Clients (Intel(R) Xeon(R) CPU from different parts of the
country.
I've played with different converter registry settings on a test machine
(Dell Optiplex) but putting .doc, docx, or .shs into different converter
options but everything remains the same so I'm not convinced that it's a
converter but rather a problem with the application itself.
Removing and re-installing the app would be my last choice due to the
geographical separation of some of the customers.
Any thoughts?
Michael
--
Terry Farrell - MSWord MVP
"Michael E. Sloan" <Michae...@discussions.microsoft.com> wrote in
message news:B5DA62C5-299A-4E1B...@microsoft.com...
These are the same instructions that were provided in a previous reply and
when I implement them through registry edits the original problem still
exist. KB973904 isn't on the clients.
Any other thoughts? I'm all ears.
"Terry Farrell" wrote:
> .
>
I have a feeling everyone is focusing on the mswrd632 error but not the
original error.
"psevin" wrote:
> .
>
Correct me if I'm wrong but I'm reading that if I have a 2007 Word document
embedded into another 2007 Word document it may not open because the source
program (Word 2007) is running.
It should be normal to be able to open an embedded document from a document.
Does this sound right to anyone?
Michael
That does not however appear to be the situation with which you are faced.
If you want to send me one of the documents that displays the problem, I
will take a look at it and see if I can find out what is causing it.
--
Hope this helps.
Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.
Doug Robbins - Word MVP, originally posted via msnews.microsoft.com
"Michael E. Sloan" <Michae...@discussions.microsoft.com> wrote in
message news:63A8B8D4-8BE5-4C36...@microsoft.com...
---
frmsrcurl: http://msgroups.net/microsoft.public.word.application.errors/Error-opening-embedded-Word-objects