Disabling Control Toolbox

[T. Adams]

I have created a document that has a macrobutton that is linked to the
EditFind macro. I also played around with creating some other macros is
visual, but decided to delete them. Now when I open the document the Control
Toolbox is present on the document (grayed out if I have protection on). I
thought maybe it was the macrobutton, so I created a test document with the
same macrobutton (but did not mess with visual basic) and I am not having the
problem. The security level is set to High on both documents. I do not want
to have to set the security level to medium because the "enable" or "disable"
macro alert will scare most people in my office into not opening the document.

 

[T. Adams]

I have created a document that has a macrobutton that is linked to the
EditFind macro. I also played around with creating some other macros is
visual, but decided to delete them. Now when I open the document the Control
Toolbox is present on the document (grayed out if I have protection on). I
thought maybe it was the macrobutton, so I created a test document with the
same macrobutton (but did not mess with visual basic) and I am not having the
problem. The security level is set to High on both documents. I do not want
to have to set the security level to medium because the "enable" or "disable"
macro alert will scare most people in my office into not opening the document.

I will also add that when I open up the design mode of Visual Basic I now
find a file under the "Normal" and "Project" tab named "ThisDocument". I
never created this file, but it does show that it involved a macro using a
name that I had created earlier, but have since deleted. I am unable to
delete "ThisDocument" and fear this is what is causing my problem.

 

[Cindy M.]

Hi =?Utf-8?B?VC4gQWRhbXM=?=,

I have created a document that has a macrobutton that is linked to the
EditFind macro. I also played around with creating some other macros is
visual, but decided to delete them. Now when I open the document the Control
Toolbox is present on the document (grayed out if I have protection on). I
thought maybe it was the macrobutton, so I created a test document with the
same macrobutton (but did not mess with visual basic) and I am not having the
problem. The security level is set to High on both documents. I do not want
to have to set the security level to medium because the "enable" or "disable"
macro alert will scare most people in my office into not opening the document.

For all intents and purposes, this document has been "marked" as containing VBA
content. You won't be able to change that. You'd need to sign the VBA project
with a digital signature of a "Trusted Publisher" in order to be able to open it
without triggering Macro security.

Or, select everything except the last paragraph mark and copy to a new document.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail

 

[T. Adams]

Thank you Cindy. This did the trick.

Hi =?Utf-8?B?VC4gQWRhbXM=?=,

For all intents and purposes, this document has been "marked" as containing VBA
content. You won't be able to change that. You'd need to sign the VBA project
with a digital signature of a "Trusted Publisher" in order to be able to open it
without triggering Macro security.

Or, select everything except the last paragraph mark and copy to a new document.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)


This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail