TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Visio Warning: Macros have been disabled From:Shawn <shawn -at- cohodata -dot- com> To:Lin Sims <ljsims -dot- ml -at- gmail -dot- com> Date:Tue, 18 Mar 2014 14:44:20 -0700
Trying to avoid an anti-rant... the macro warning is in place because
Microsoft developers added too much 'power' to the vb scripts that can
attach themselves to any Office document or project. It really is
ridiculous that the products (and your entire computer) can be so easily
Anyhow, here are the steps you need to make (just don't load up any unknown
3. Trust Center side-tab
4. Trust Center Settings... button
5. Select Disable all macros with warning (and/or other appropriate to your
6. Click OK.
On Tue, Mar 18, 2014 at 11:31 AM, Lin Sims <ljsims -dot- ml -at- gmail -dot- com> wrote:
> 1. Our graphics department migrated from Visio 2007 to Visio 2013 within
> the last couple of weeks.
> 2. Our standard graphic format for documentation is SVG.
> 3. Visio 2003 didn't save drawings to SVG quite right unless you used a
> couple of macros to save it with.
> 4. Any time we open a .vsd file in Visio 2013 that was created in Visio
> 2007, we (or at least I) am removing the macros from the Developer tab
> because Visio 2013 saves properly to SVG and they aren't needed anymore.
> Sometimes (but not ALL the time), reopening the files that have had the
> macros removed results in a yellow bar warning in Visio that macros have
> been disabled.
> Checking the list in the Developer tab shows no macros listed for the
> diagram (as is right and proper).
> So why the warning? And how do we get rid of it?
> Note that any diagram with the unneeded macros left in it ALWAYS comes up
> with that warning. The whole point of removing them is to get rid of the
> warning, but it seems to work on some random principle we haven't guessed.
> Lin Sims
> Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp
> enhancements, and more. Read all about it.
> Learn more: http://bit.ly/NNcWqS
> You are currently subscribed to TECHWR-L as shawn -at- cohodata -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.