[Mr B]

Yeah I suppose that's correct. I guess it'd be better to say:

Is there any way that if the directory it's saving to isn't found, that it
could default back to the normal save path?

That way if they were saving to the network, it would work fine, but if they
were saving to that Temp folder on C, it'd reject out and go back to the
normal path to save stuff to...

And yes, everyone's file locations settings have been changed. We push out
software via ZenWorks/Novell and it's all encorporated into that.

"Idaho Word Man" wrote:

After answering the question I THOUGHT you asked, I took the time to read the
question you actually asked in your second paragraph.

How did you set Word to "automatically save to a network drive"? Did you
just set everybody's File Locations tab to a directory on your server? If
that's all you did, the answer to your question is "You really don't want to
force every document that is opened from an existing location [to] default to
save to the network drive." If your company is anything like every company I
have ever worked with, you have a complex structure of directories on your
server. Each department or organization probably has directories and
subdirectories for different kinds of documents.

If every document defaulted back to the main directory on the network drive
every time it was saved, every person who saved a document would have to
navigate back to the directory he/she needed to keep the document in -- every
time each document was saved. Anybody who forgot to navigate back to the
right directory would end up with two copies of the document -- one in the
main directory of the network drive and one in the subdirectory it had
originally been opened from.

Perhaps you have a much more sophisticated system that this, but if you
don't I think you'd find there was a lot more wasted effort involved in
navigating back to the correct directory every time you save than there is
with the occasional lost document.