Hi Steve,

Thanks for the reply. Judging by the number of posts I was beginning to
think every one on this NG had gone away on early holidays.

I was going to respond with the information below.  In cases like this
I usually go back and try as many of the steps as I can tolerate
repeating one more time before posting a response/followup. I usually
write the reply from memory and then go back through the steps and
check that I have actually done what I write.

My response to you was going to be as quoted (below).
"As to my problem - No such luck. There are no other copies other than
backups/saved copies in known locations.

The template is four years old and originally created in Word 2K.
Since that time I have had two different machines.  The current one is
a laptop which has been upgradedseveral times first from  Windows 2000
to Windows XP then Office 2000 to XP (2003) and subsequently re-imaged
a couple of times to bring it back to Standard Desktop Environment.

I have also 'cleaned' the template using the  VBA Code Cleaner.  That
is the  template has been 'cleaned' both before and since discovering
the problem.  I have also re-created the template by exporting all of
the modules etc. "

In checking my response I decided to recreate the template again and
import the code into a new template.  As I was testing and going
through my steps I noticed that I had another addin in the startup
folder.  This was the Dataviz (documents to go) DVZWDAddin.dot.  I
didn't recall noticing that before although I have had Documents to go
for a while.  Ahh You bastard I thought!. So I removed it hoping that
the problem was this simple.  I am glad to say it wasn't <g>.

After removing that addin I then noticed something else.  Whenever I
opened the workfile based on the template that had the reference to my
addin I would get a blank messagebox popping up.  I was opening the
file from the MRU list.  This has not happened before but I can't be
sure I had repeated that sequence of events.  You know, that file
attached to that template from that spot etc.  (I can get paranoid - or
is that anal retentive?)  in cases lke this.  I could not work out
where this message was coming from.  I still haven't!

But anyway, to cut a Long story short, I discovered a reference in my
normal.dot to a richtext control (tom - Riched20.dll) that I have been
playing with of and on for some time.  Taking this out of normal.dot
seems to have done the trick.

I hope <g>.

I will believe it when I look again after I wake up and find it still
working <vbg>.

I must be dreaming because I am sitting here writing this in my
nightshirt having been woken up by a phone call from my wife (who is at
work) asking me to look at something in an email.  pinch, Ouch!

Cheers and happy Christmas,

TonyS.