Replies

Thanks so much. This worked perfectly!

What a relief! I’d envisioned staying up all night installing. Thanks to both of you.

What a relief! I’d envisioned staying up all night installing. Thanks to both of you.

Thanks for your reply. I checked WMP, but will take a look to see if there are any other programs I need to look at.

Thanks for your reply. I checked WMP, but will take a look to see if there are any other programs I need to look at.

Thanks for the reply & screen shot. I had already raised all the sliders. In fact, all the sliders were at their highest point when I looked at them — I think because I’d already moved the master volume to high.

Thanks for the reply & screen shot. I had already raised all the sliders. In fact, all the sliders were at their highest point when I looked at them — I think because I’d already moved the master volume to high.

Thanks for your reply. I’m away from that computer at the moment, but will check this as soon as I can.

Thanks for your reply. I’m away from that computer at the moment, but will check this as soon as I can.

Your macro runs fine on my Windows XP/Office 2002 machine. We had a few similar problems when converting from Windows NT/Office 97, but ours were solved when we changed our macro security settings to security level low or medium and our trusted sources to “trust all installed add-ins and templates” and “trust access to visual basic project”.

(Edited by gwhitfield on 29-Jan-03 21:03. Hot links added)

I knew about the temp files. http://www.mvps.org/word/FAQs/AppErrors/Lo…ilesContent.htm%5B/url%5D has instructions for dealing with them & other disk messies. However, we also have another issue, which is that we’re using a set of automated templates (plus an add-in) programmed by others. I am now working on the next release & we have not so far experienced any “read onlification” while testing the new add-in.

I tested your procedure on a read-only file and got a “Path/File access error” at the first line starting with “Kill.” Since the file was on my C drive, I’m pretty sure this means Word won’t let me kill a read only file. Your procedure was very similar to one of my attempts, which also gave me an error message when attempting to kill the read-only file.

I already had the file “saved as” in my macro. What I wanted to do was delete the read only file so that I could then “save as” again using the original filename. (I would then kill the file with the wrong name.) Word is occasionally turning users’ files into Read-Only files as they are working on them, and I was hoping to give them a quick way to recover from this. I’m sure Kevin’s solution would work, but I don’t know how to use VB Script & haven’t had the time to try to figure it out.

I use the following code snippet to get at things in an Add-In template:

Dim Tplt As Template
For Each Tplt In Templates
If Tplt.Name = “MyTemplate.dot” Then Exit For ‘Of course, you do need to know the name of the Add-In template!
Next Tplt

‘You can now use Tplt to get at whatever is stored in your Add-In, for example:

Tplt.AutoTextEntries(“My AutoText”).Insert Where:= _
Selection.Range, RichText:=True

Hope this helps!

I recently had a similar problem: I had two add-in .dot files in my Startup directory, both of which had custom menus and toolbars. One day the custom menus disappeared, but not the custom toolbars from those same templates. I still don’t know what caused the problem, but the problem went away when I renamed my Normal.dot, thus causing Word to create a pristine one. When I did that, the custom menus in the two add-ins reappeared. Perhaps my old Normal.dot was corrupt in some way, or perhaps it had gotten too large. (I have to admit that it was *very* large.) I use Word XP.

I can’t answer your question, but our office has a similar problem: when some of our people click on the “Close Window” x on the menu bar (and also when they choose File | Close) Word closes the entire program. We would love to know a fix for this. Did you ever come up with a solution?