Dag nab it!
I had just finished replying and lost my phone connection and lost what I typed. Oh well, maybe I'll get better words this time.


Quote Originally Posted by Tommy
Just to present the steps:

I had the VBIDE open, I picked the X in the upper right hand corner, the template closed
There is no need to open the VBIDE. The macro should be run using the "Test Toolbar" or via the Tools |acros menu in Word.

and normal was highlighed when the dialog box poped up.
What dialog box?

Also noted was the PDFmaker was still in the project which implies that it was not closed yet and normal was either in the process of closing and didn't due to error or the error occured before Normal was told to close.
PDFMaker is not going to close until you tell Word to close and it will difficult, if not impossible, to see the sequence of closing.


I can open a document, open the template, run macros, close template, close doc, close Word, then get error.
Good, that confirms my assertion in my previous posting.

On a another note, Word keeps track of the buttons that are added by using the .Tag property, even though when you loop through the "Standard" buttons the .Tag properties are blank. I read that somewhere so don't hold me to that.
The ID property identifies the buttons. The Tag property is not used by Word, rather it is reserved for the app to use in any which way including loose.