Siging a VBA project in Windows 2003 Server

W

Whale Skinner

We have some spreadsheets containing VBA code that are used within the
company. The code was developed in Windows 2000 Server and was signed
by a digital certificate created by me using the selfcert.exe utility.

Now I have a new machine with Windows 2003 Server on it. I have
created a new certificate using the Office Tools | Digital Certificate
for VBA Projects utility. I have assigned that certificate to my
project in the Excel project.

Now it works fine without prompting me to enable macros on my machine.
But when I give this spreadsheet to another user, they get a message:

"A protected module can't be displayed. This error has the following
cause and solution. There is a compilation error in the code of the
specified module, but it can't be displayed because the project is
protected.
Unprotect the project, and then run the code again to view the error."

The project is protected and we wish to keep it that way to prevent
others from mucking with it.

How do I sign a VBA project in Windows 2003 Server so that it will run
on another machine?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top