If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
"Do you want to replace the existing Normal?"
Hi Steve,
Well... for those who do crazy things in Word that behavior could be expected. g One item I don't understand in your post though, what is a 'loose style definition in the body of the document' and how could it cause corruption in Normal.dot?? Please post all follow-up questions to the newsgroup. Requests for assistance by email can not be acknowledged. ~~~~~~~~~~~~~~~ Beth Melton Microsoft Office MVP Word FAQ: http://mvps.org/word TechTrax eZine: http://mousetrax.com/techtrax/ MVP FAQ site: http://mvps.org/ "Word Heretic" wrote in message news G'day Beth, yeah - that's also a valid point, the flipside is my normal stays stable for yonkers, I have everything set 'nicely' and it still wants to be petted and saved. Word Happens... Additionally, I have renamed Normal before and still had word spazz out with a corrupt Normal in no short time. True, I am a developer and always doing crazy things with Word. But the point is certain combinations of actions can kill normal and it has nothing to do with saving it overly regularly - excluding having Fast Saves on of course which will kill it rapidly. Example sequence, using a toolbar from a global template, mod it from normal context, then from its parent, then from normal, then from another template, then from normal again. Close Word, move this template elsewhere. Create another toolbar with the same name in a global template and repeat. Quit Word, load both templates, enjoy. These probably a few caveats in there but when I play silly buggers with the toolbar collection programatically and I screw up the context, all hell breaks loose rapidly and normal is dead again. As for add-ins - if they create / destroy commandbars which is a popular novice technique that isn't dangerous then you can get this behaviour. Etc. Hell, a loose style definition in the body of the document could cause it :-) Steve Hudson - Word Heretic Want a hyperlinked index? S/W R&D? See WordHeretic.com |
Thread Tools | |
Display Modes | |
|
|