I am not sure what you are telling me -- that I have to run the programs with
low or medium security? If so, that defeats the purpose of assigning digital
certificates -- so that I can have my security at a higher level.

I have tried everything. Two of my projects, one of them that contains many
of my macros for running userforms and other macros in other projects, always
opens with the design mode button highlighted in the VB Editor. One of these
templates has a Digital Certificate assigned. The other project only contains
modules and has no Active-X controls. When I try to click on this design mode
button to turn off design mode in either of these projects, I get a "macros
in this project are disabled" -- The only way I can run these programs is
with security set to low.

I have since narrowed it down to one offending Project by deleting all the
references in my MacroReports project that contains the macros for running
other projects and then one by one adding the references to these other
projects back in. There was only one project that caused the design mode
button to be highlighted and thus generate the "macros are disabled blurb"
when trying to run any of the macros in the MacroReports project. I have
tried creating a whole new template for the offending project and copying the
userform and code to this new template, but it did not solve the problem.
What would cause a particular project to say the macros are disabled?

In case anyone is interested, I just discovered that the digital certificate
for this project had to be sgined in VBA. I had sgined it using Tools,
Options, Security in the document window, but when I checked under Tools,
Digital Certificate in VBA, it was not signed there. I am still unclear as to
how this all works, but now my project's macros are not disabled using
security of high.