A
Andy Smith
Hiya,
We point Word's Startup folder to a UNC path. This is causing Word to take
upwards of 10 seconds to respond. If I change the Startup path to a drive
mapping the problem goes away.
Our Startup folder contains special templates, so we can't use drive
mappings as I don't want users to browse them.
Is there a fix for this problem?
Thanks
We point Word's Startup folder to a UNC path. This is causing Word to take
upwards of 10 seconds to respond. If I change the Startup path to a drive
mapping the problem goes away.
Our Startup folder contains special templates, so we can't use drive
mappings as I don't want users to browse them.
Is there a fix for this problem?
Thanks