Word, Getting away from Normal.dot...

Getting away from Normal.dot...

Author	Message
TC Canfie #1 / 4	Getting away from Normal.dot... Greetings, First post to this group so bear with me... In visual basic, we are creating an instance of Word and customizing some menu items and toolbars in code. The user is then allowed to work in that session of word. After they are done, the menu items and toolbars are put back. ...Now, from what I know so far(and from what the voices in my head tell me)..., this apparantly is BAD DESIGN because if we are making changes to their NORMAL.DOT, they (the user) may loose some custom macros or other stuff they already had in their original normal.dot... Also, if they open word outside my app, they things really get funny. What I would like to do...I think... is Open an instance of Word using something BASED on normal.dot, but is not normal.dot. Make the changes that we need to that something (menus, toolbars, etc.)... Make sense??? I am not sure what I am asking, but do I need to just create another template and add it to the templates collection and reference it in code?? ANY HELP IS GREATLY APPRECIATED Todd Canfield Oregon Department of Revenue
Sat, 16 Apr 2005 01:42:42 GMT

Steve Atkinso #2 / 4	Getting away from Normal.dot... Copy normal.dot as abnormal.dot. Then use the /t switch to open winword.exe with a blank document based on abnormal.dot. Syntax is [path]/winword.exe /tabnormal.dot. Don't forget to use quotes from the beginning of the line through '.exe' if you have spaces in your path. The switch should not be included in the quotes. Quote: > Greetings, > First post to this group so bear with me... > In visual basic, we are creating an instance of Word and customizing > some menu items and toolbars in code. The user is then allowed to > work in that session of word. After they are done, the menu items and > toolbars are put back. > ...Now, from what I know so far(and from what the voices in my head > tell me)..., this apparantly is BAD DESIGN because if we are making > changes to their NORMAL.DOT, they (the user) may loose some custom > macros or other stuff they already had in their original normal.dot... > Also, if they open word outside my app, they things really get funny. > What I would like to do...I think... is > Open an instance of Word using something BASED on normal.dot, but is > not normal.dot. Make the changes that we need to that something > (menus, toolbars, etc.)... Make sense??? > I am not sure what I am asking, but do I need to just create another > template and add it to the templates collection and reference it in > code?? ANY HELP IS GREATLY APPRECIATED > Todd Canfield > Oregon Department of Revenue
Sat, 16 Apr 2005 03:50:10 GMT

Marily #3 / 4	Getting away from Normal.dot... You're certainly right to avoid changing normal.dot. Apart from annoying the user, it will out-and-out fail in some cases. Rather than making these changes on the fly, another approach is to create a template with menus toolbars set up as you need. Then at run time load that template as an add-in. Quote: > Greetings, > First post to this group so bear with me... > In visual basic, we are creating an instance of Word and customizing > some menu items and toolbars in code. The user is then allowed to > work in that session of word. After they are done, the menu items and > toolbars are put back. > ...Now, from what I know so far(and from what the voices in my head > tell me)..., this apparantly is BAD DESIGN because if we are making > changes to their NORMAL.DOT, they (the user) may loose some custom > macros or other stuff they already had in their original normal.dot... > Also, if they open word outside my app, they things really get funny. > What I would like to do...I think... is > Open an instance of Word using something BASED on normal.dot, but is > not normal.dot. Make the changes that we need to that something > (menus, toolbars, etc.)... Make sense??? > I am not sure what I am asking, but do I need to just create another > template and add it to the templates collection and reference it in > code?? ANY HELP IS GREATLY APPRECIATED > Todd Canfield > Oregon Department of Revenue
Sat, 16 Apr 2005 05:02:44 GMT

Suzanne S. Barnhil #4 / 4	Getting away from Normal.dot... Instead of tinkering with Normal.dot at all, add your toolbars, menus, etc., by use of a global template (add-in) in Word's Startup menu. It will be loaded along with Normal.dot at startup, and all its toolbars, menus, AutoText, etc., will be available to users along with those of Normal.dot. For more, see http://www.mvps.org/word/FAQs/Customization/WhatTemplatesStore.htm -- Suzanne S. Barnhill Microsoft MVP (Word) Words into Type Fairhope, Alabama USA Word MVP FAQ site: http://www.mvps.org/word Quote: > Greetings, > First post to this group so bear with me... > In visual basic, we are creating an instance of Word and customizing > some menu items and toolbars in code. The user is then allowed to > work in that session of word. After they are done, the menu items and > toolbars are put back. > ...Now, from what I know so far(and from what the voices in my head > tell me)..., this apparantly is BAD DESIGN because if we are making > changes to their NORMAL.DOT, they (the user) may loose some custom > macros or other stuff they already had in their original normal.dot... > Also, if they open word outside my app, they things really get funny. > What I would like to do...I think... is > Open an instance of Word using something BASED on normal.dot, but is > not normal.dot. Make the changes that we need to that something > (menus, toolbars, etc.)... Make sense??? > I am not sure what I am asking, but do I need to just create another > template and add it to the templates collection and reference it in > code?? ANY HELP IS GREATLY APPRECIATED > Todd Canfield > Oregon Department of Revenue
Sat, 16 Apr 2005 05:10:07 GMT

Page 1 of 1

[ 4 post ]