P
PatD
I've seen several messages about opening Word and getting the message that
Word has stopped working.
I've used Word since V3 and have not had problems until Word 07 running on
Vista Ultimate. I've had the problem on 2 computers, both had Office
installed from scratch on Vista, with no updating involved. SP1 made no
difference.
After getting the problem I can reboot and it will go away. SP1 fixed the
blue screen problem with Excel, but the word startup problem has persisted.
It seems to happen just before the styles load on the ribbon. (That may
point to normal.dotm as suggested on several posts.)
On my new workstation, Word worked for about 2 weeks and then started with
the same startup problem. It seems to have something to do with IE running,
but I'm not sure.
I just renamed Normal.dotm and the problem has gone away for now.
It would seem to me that Microsoft can write code to recover from a few of
these causes. Get us out of Error Message Hell that puts out these nebulous
messages and gives no guidance on what to do. Microsoft, your better than
that.
Figure it out. Trap the error, and either allow the user to fix it on the
fly or provide a link to a help topic.
Word has stopped working.
I've used Word since V3 and have not had problems until Word 07 running on
Vista Ultimate. I've had the problem on 2 computers, both had Office
installed from scratch on Vista, with no updating involved. SP1 made no
difference.
After getting the problem I can reboot and it will go away. SP1 fixed the
blue screen problem with Excel, but the word startup problem has persisted.
It seems to happen just before the styles load on the ribbon. (That may
point to normal.dotm as suggested on several posts.)
On my new workstation, Word worked for about 2 weeks and then started with
the same startup problem. It seems to have something to do with IE running,
but I'm not sure.
I just renamed Normal.dotm and the problem has gone away for now.
It would seem to me that Microsoft can write code to recover from a few of
these causes. Get us out of Error Message Hell that puts out these nebulous
messages and gives no guidance on what to do. Microsoft, your better than
that.
Figure it out. Trap the error, and either allow the user to fix it on the
fly or provide a link to a help topic.