Winword.exe has generated errors opening a file

[triciab]

I have a user that receives the above error message when opening a few files
that were all created using a template created by someone in our hq.
I have tried:
1. Deleting the normal.dot
2. Updating the application per MS's automated update process
3. Uninstalling and reinstalling Office
4. Looking for files in startup or templates folders (based on location
indicated in options + file locations) - none except normal.dot (after
recreation)
5. Opening the file on another computer (all machines have W2K O/S) - this
worked on mine (using Office 2003) but not on any other computer (Office 2000)
6. Tried logging in on the user's computer as another user (all have admin
rights)
7. Opening Word with the /a command (this works but I read somewhere that
should NOT be used permanently)
8. Checked the registry - didn't find anything unusual but don't know enough
to dig too deep
9. So many other things I can't even remember them all.

I've had this problem with files of a few different users on different
computers and I'm afraid by the time the deadline for turning these files in
hits, I'm going to be bombarded.

I would sincerely appreciate any help or ideas. I've been researching and
working on this one for way too long!

Thank you - TriciaB

 

[Graham Mayor]

It sounds like there is some minor corruption in these documents - probably
introduced by the original template, and probably not helped by working with
two Word versions. The document may, for example have some Word 2003
formatting option that was not available in Word 2000. Check the
compatibility options.

From the Word 2003 file > open dialog, select the file and then click the
little arrow at the right of the Open button and select Open & Repair. That
may fix it.

 

[triciab]

Graham,

I actually tried that. One of the multitudes of things I tried but didn't
work. I agree with your assessment that the problem is probably with the
original template. Unfortunately, it's a company-wide thing and it's pretty
complex so I don't think I can reconstruct the template. I think I'm just
going to tell the users to use the /a command to get through this year.
There's already another solution in place going forward.

Thanks again for your help!

Tricia

 

[Graham Mayor]

Can you get at the template to open and repair *it*? Or does it exist in a
multitude of copies throughout the organisation?

Winword /a eliminates all the external variables - see
http://word.mvps.org/FAQs/AppErrors/ProbsOpeningWord.htm

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>