: : > But what if the changes are something I don't like once I say yes?
: Whatever
: > I did, I didn't mean to. If it messes things up, would you be able to
: help
: > me get it back to whatever "normal" is?? :-D
:
: Do not say Yes unless you know what changes were made.
: Indeed, you may have mage 1 intended change, but other (unintended)
changes
: would also get saved if you answer Yes.
:
: One of the commandments of my, and most experienced, Word programmers is
: that the Normal template should have as little as possible in it.
:
: In particular, application specific macros belong in a
: separate template, instead of in the Normal template.
:
: Indeed, many, including moi, would argue that the Normal template should
be
: read-only.
:
: I remove the read-only setting ONLY when I wish to explicitly change
: Normal.dot.
:
: Note that the ONLY code in my own Normal template is given below AND the
: template is read-only.
: In my case, I've actually included the real code in a class in a VB 6
: ActiveX DLL, which runs faster and protects the code from prying eyes. I
: could have instead included the code within the template. but chose not to
: do so.
:
: Properly writtem such code and DLL can be used with more than one version
of
: Word.
:
: Option Explicit
: Public clsWordVBNormal As WordVBNormal
:
: Public Sub AutoClose()
: SetupClass
: clsWordVBNormal.clsAutoClose
: End Sub
:
: Public Sub AutoExec()
: SetupClass
: End Sub
:
: Public Sub AutoExit()
: SetupClass
: clsWordVBNormal.clsAutoExit
: End Sub
:
: Public Sub AutoNew()
: SetupClass
: End Sub
:
: Public Sub AutoOpen()
: SetupClass
: End Sub
:
: Public Sub ResetToolsOptionsView()
: SetupClass
: clsWordVBNormal.clsResetToolsOptionsView ActiveDocument
: End Sub
:
: Private Sub SetupClass()
: If TypeName(clsWordVBNormal) <> "WordVBNormal" Then
: Set clsWordVBNormal = New WordVBNormal
: clsWordVBNormal.SetClass Application
: End If
: End Sub
:
I appreciate the information. I only wish I understood it.
: