>>I don't see anything there that would modify the Normal template. All I can suggest is taking it apart bit by bit to see which things you're doing trigger the prompt. Or just set oWord.DisplayAlerts to .F.
>>
>>Tamar
>btw this anly happens in the current version of Office
>
>
>oWord.DisplayAlerts to .F. did not change anything.
>by the way the help on the dialog read like this:
>
>"This error is commonly encountered when a read lock is set on the file that you are attempting to open. Possible reasons for this:
>Another user has the file open, either on the same computer that you are using, or on another computer.
>Word crashed at some point in the past and left a read lock on the file.
>Another application has an exclusive lock on the file, preventing Word from opening the file.
>A custom application is running and has opened this file (possibly on another user's computer). It may have opened the file using an incorrect method.
>To correct this problem, close all applications, restart Word and try to open this file again. If this does not work, examine the properties of the file to determine if someone else has it open. Occasionally a phantom process (dead or disassociated program) may have a lock on the file, and the only means of clearing it is to restart your computer.
>For more information, see Microsoft Knowledge Base article 918593."
>

I haven't run into it, but I haven't done more than testing with automating Word 2010. (That is, no clients have needed it automated yet.)

The only other thing I can suggest is to null all the variables that reference Word objects that you can before you try to close. Keep only the variables for the objects you'll still talking to.

Tamar