See
http://word.mvps.org/FAQs/AppErrors/LockedFiles.htm. The temp files are
what are causing your problems. You might also want to read “WD: How Word
for Windows Uses Temporary Files†at
http://support.microsoft.com/?kbid=211632
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.
Chris said:
The website referenced is helpful.......provided all this is happening on
the same computer. Unfortunately, if a process has copied the document from
another computer then how would these temporary, "locking" or "owner" files
apply? Obviously they could not as, in my instance, no other process on the
machine is accessing these files. I believe there is a problem with Word not
doing a good job of cleaning up after itself relative to the tmp files it
does create on a given machine relative to an instance of Word especially
if, as we are, processsing document after document in assembly line fashion.
The other possiblity is there is something embedded within the document
itself that is "incomplete" for lack of a better term that flags Word that
the document is still being editted, somewhere. This could happen if the
instance of Word on the other machine was terminated abruptly and the
document was left "hanging". I have been wrestling with this issue for
many, many weeks now and am dying for a resolution.