I will say it again, they are not opening the template. They are (at least I think that is what you are saying) calling the template.
I have no idea what you mean by "field window".
A userform is a separate kind-of dialog that is used to gather user information.
" why I needed autoexec vs autoopen. "
I do not think you need either.
"they are advised to not use the template at all."
So they start to use the template...and then are fro
zen out of it
? Fair enough, but you still do not need AutoExec, or AutoOpen. What are the requirements (and how are these determined) that decide whether to proceed further?
In any case, here is a simple example of what I am talking about.
You have a dot file (the template). It has however many userforms you need (for the fields to be filled in). The FIRST userform is the one that decides to go further, or not.
In the ThisDocument module, on Dpcument_New - the template is called, the first userform is shown.
Code:
Option Explicit
Private Sub Document_New()
UserForm1.Show
End Sub
In this simple example, I have a textbox and a commandbutton. Here is the code for the commandbutton.
Code:
Option Explicit
Private Sub CommandButton1_Click()
If TextBox1.Text <> "yadda" Then
Msgbox "Requirements not met. Template will close."
ActiveDocument.Close
Unload Me
Else
' show the other "fields"
End If
End Sub
So, when the button is clicked, if the textbox is NOT "yadda" - these are your requirements - the ActiveDocument is closed, and the userform unload.
That means, if the requirement is not met (in this case the text is not "yadda"), there is a message stating requirements not met, the new document closes (never actually shown), the userform closes...and things stop.
If the requirements ARE met - the Else of the IF statement - you proceed with the other field fillin stuff in the other userforms.
No AutoExec. No AutoOpen.