There are two main problems with providing a 'standard' normal.dot file.
1. It becomes tempting to share normal.dot which stifles user creativity and
in a worst case scenario its corruption can stop the whole workforce.
2. Replacing it on log-in loses users' personalisations which reduces
productivity and annoys the hell out of experienced users for no good
reason.
Any standards required can be provided in the document templates required
for company documents.

Signature
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP
My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Cindy M -WordMVP- wrote:
Understood regarding mucking around with the normal.dot file. In this situation, the workstation in question is used for a specialized application only. Various people must use this computer to run the app. Not a problem except that the app uses MS Word to generate reports and unless the margins are set a certain way, attempting to print it hangs the server's print spooler! I'd rather not go along the route of trying to persuade the vendor to modify the app. Trying various print drivers and printers did not help.
Keith
> There are two main problems with providing a 'standard' normal.dot file.
>
[quoted text clipped - 33 lines]
> > This reply is posted in the Newsgroup; please post any follow
> > question or reply in the newsgroup and not by e-mail :-)
Graham Mayor - 15 Jun 2004 06:42 GMT
Understood - in those circumstances you need to ensure that all users on
this work station use the same Word version and the same copy of normal.dot.
This then becomes a networking issue.
I would have thought also that if a vendor supplies an app. usually at great
cost, that the user should not have to jump through hoops to make it work as
intended. This sounds like poor programming to me :(

Signature
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP
My web site www.gmayor.com
Word MVP web site http://word.mvps.org
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
> Understood regarding mucking around with the normal.dot file. In this
> situation, the workstation in question is used for a specialized
[quoted text clipped - 57 lines]
>>> This reply is posted in the Newsgroup; please post any follow
>>> question or reply in the newsgroup and not by e-mail :-)
Hi Graham,
> There are two main problems with providing a 'standard' normal.dot file.
>
> 1. It becomes tempting to share normal.dot which stifles user creativity and
> in a worst case scenario its corruption can stop the whole workforce.
If anyone ever comes along and says they want to 1. lock down Normal.dot and
2. force users to share it (happens often enough in the German NGs, BTW), then
I agree with you totally.
> 2. Replacing it on log-in loses users' personalisations which reduces
> productivity and annoys the hell out of experienced users for no good
> reason.
Well, yes-and-no. Whichever way the decision goes, the users need to be
trained. There's the problem with NOrmal.dot that it tends to "go bad" and
need replacing every once in a while, and under those circumstances one could
lose everything, too. But if the users are trained to place their
personalizations in a global template, this gets around that problem, as well.
Then the only obstacle would be personalized AutoText entries.
In any case, I understood the original question to mean that they just wanted
certain margins. And in this case, the "customized" Normal.dot would only have
to be copied over once.
OTOH, if Keith had mentioned originally that it was just for one particular
application, I'd have suggested creating a template specific for that purpose
:-)
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 8 2004)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)