Actually, the right way is for you to go to each machine and create a link
from their (users) machine to the network template file location.
That way, you avoid them having the ability to even open the original.
There are several ways of truly networking a template, BUT, each
necessitates going to each machine ONCE, to create the primary link. AFAIK,
there is no way to get away from going to the individual machines at least
once.
Check out this old post which describes one way.
http://tinyurl.com/zd66
Post back if you wish additional procedures to accomplish networking
templates.
--
HTH,
RD
==============================================
Please keep all correspondence within the Group, so all may benefit!
==============================================
Pete said:
Which would be the best way to keep a template on a public drive from
being written to by idiots who can't read. We have a timesheet template on a
public drive and we have told everyone to open it, save as template on their
own drive. Close it and then File -- New -- template and select the
timesheet template to create a copy. The problem we are having is that
people open the darn thing and start writing to it after removing read only
from properties?