[Tony Jollans]

There are (at least) two different issues here.

Operating system (e.g. Windows) locks must be placed somewhere where the
operating system can find them and relate them to the locked resource.

Where appropriate (e.g. concurrent updating in multi-user environments),
application-level (e.g. Word) locks must be placed somewhere where other
instances of the application can relate them to the original resource. I
don't think any current versions of Word require such locks.

Application temporary files should normally be placed in local temporary
space. Instead of using the %temp% directory provided by Microsoft's own
operating system specifically for this purpose, Word chooses to use the
document's source folder. This does confuse users and does cause problems
when working on networked devices and/or removable media.

The only time there is any real reason to use a file's source folder for
temporary work space is when saving a file - to make sure the file is
properly saved before removing the original - overwriting in place is
inherently risky.

I am inclined to agree that Word's behaviour would be considered bad
programming practice, and I can't think of a single thing in its favour.

--
Enjoy,
Tony

"Terry Farrell" schreef in bericht
...
Well if the temp locking file was placed in your temp folder, how would
someone else with access to the same folder on the server be aware that
the document was already open and stop them from opening and editing the
document at the same time as you. Chaos would reign.

Terry

"LurfysMa" wrote in message
...
On Mon, 26 Mar 2007 06:50:03 +1000, "Aalaan"
wrote:

The answer is certainly no. Word makes use of various temporary files as
it
works (excuse pun). Saving to portable media is invariably too slow and
files get easily corrupted. You *may* be OK loading *from* but why not
just
get into the habit of copying to the main hard drive and always working
from
there?

This is yet another bug that we have had for so many releases. I guess
M$FT is too poor to fix bugs.

The temp files should all be in a temp directory, not cluttering up my
personal folders and certainly not written to floppies.

And there is no excuse for a M$FT application using the M$FT file
system to ever crash or have corruption.

This is just ****ty code. It would not get a passing grade in an
undergraduate programming course. Total BS.

--
Running Word 2000 SP-3 on Windows 2000