D
Dwain Gleason
I have created an Excel document on my development machine: Windows XP SP1a,
Excel 2003. This document contains Macros that I want my users to be able to
use without being bothered by the macro warning box at startup. I have
obtained a Verisign code signature digital ID for VBA and have used the
instructions in Office Help to sign the VBA project with the installed
certificate. This seems to work OK in my development environment.
When I first gave the workbook to an Excel 2000 user with Macro Security set
to Medium, when they opened the workbook and tried to fire a macro they were
told that macros had been disabled. This happened even when restarted with
LOW macro security!
When looking at the digital signature information in the VBA editor, I found
the error that "Windows does not have enough information to verify this
certificate." I found a workaround on both the MS Knowledge Base
(http://support.microsoft.com/default.aspx?scid=kb;en-us;816895) and the
Verisign knowledge base
(http://searchsupport.verisign.com/s....verisign.com/content/kb/vs17614.html#Goto699)
that indicated that the end user had to download and import the code signing
intermediate CA in the intermediate certificate store on their machine. I did
this following their instructions.
After restarting Excel 2000 in Medium Security mode, I still get the same
response - Macros have been disabled - when trying to run a macro. When
viewing the Macro information in the VBA editor on the client machine there
are no errors - the window displays that there are no problems with the
certificate. If the client changes to LOW security and opens the file the
macro runs as expected, but I don't want to have all my clients set their
security settings to LOW - that defeats the purpose of having a $400 Verisign
certificate on my code.
Is there any way to get around this problem on my Excel 2000 clients?
Excel 2003. This document contains Macros that I want my users to be able to
use without being bothered by the macro warning box at startup. I have
obtained a Verisign code signature digital ID for VBA and have used the
instructions in Office Help to sign the VBA project with the installed
certificate. This seems to work OK in my development environment.
When I first gave the workbook to an Excel 2000 user with Macro Security set
to Medium, when they opened the workbook and tried to fire a macro they were
told that macros had been disabled. This happened even when restarted with
LOW macro security!
When looking at the digital signature information in the VBA editor, I found
the error that "Windows does not have enough information to verify this
certificate." I found a workaround on both the MS Knowledge Base
(http://support.microsoft.com/default.aspx?scid=kb;en-us;816895) and the
Verisign knowledge base
(http://searchsupport.verisign.com/s....verisign.com/content/kb/vs17614.html#Goto699)
that indicated that the end user had to download and import the code signing
intermediate CA in the intermediate certificate store on their machine. I did
this following their instructions.
After restarting Excel 2000 in Medium Security mode, I still get the same
response - Macros have been disabled - when trying to run a macro. When
viewing the Macro information in the VBA editor on the client machine there
are no errors - the window displays that there are no problems with the
certificate. If the client changes to LOW security and opens the file the
macro runs as expected, but I don't want to have all my clients set their
security settings to LOW - that defeats the purpose of having a $400 Verisign
certificate on my code.
Is there any way to get around this problem on my Excel 2000 clients?