Hey your macro's in this spreadsheet are not signed. My PC security system flagged this as a security risk. Can you correct this?
Other than this it looks good. I wasn't able to run any macros though...
From Help:
About macro security
About security levels and what they mean
The following information summarizes how macro virus protection works under each setting on the Security Level tab in the Security dialog box (Tools menu, Macro submenu) under different conditions. Under all settings, if antivirus software that works with Microsoft Office XP is installed and the file contains macros, the file is scanned for known viruses before it is opened.
High
Unsigned macros
Macros are automatically disabled, and the file is opened.
Signed macros
The source of the macro and the status of the signature determine how signed macros are handled.
A trusted source. Signature is valid.
Macros are automatically enabled, and the file is opened.
An unknown author. Signature is valid.
A dialog box is displayed with information about the certificate. Macros can be enabled only if the user chooses to trust the author and certification authority. A network administrator can lock the list of trusted sources and prevent the user from adding the developer to the list and enabling the macros.
Any author. Signature is invalid, possibly because of a virus.
User is warned of a possible virus. Macros are automatically disabled.
Any author. Signature validation is not possible because public key is missing or incompatible encryption methods were used.
User is warned that signature validation is not possible. Macros are automatically disabled.
Any author. The signature was made after the certificate had expired or had been revoked.
User is warned that the signature has expired or been revoked. Macros are automatically disabled.
Medium
Unsigned macros
User is prompted to enable or disable macros.
Signed macros
The source of the macro and the status of the signature determine how signed macros are handled.
A trusted source. Signature is valid.
Macros are automatically enabled, and the file is opened.
An unknown author. Signature is valid.
A dialog box is displayed with information about the certificate. The user is prompted to enable or disable macros. The user can choose to trust the developer and certification authority.
Any author. Signature is invalid, possibly because of a virus.
User is warned of a possible virus. Macros are automatically disabled.
Any author. Signature validation is not possible because public key is missing or incompatible encryption methods were used.
User is warned that signature validation is not possible. User is prompted to enable or disable macros.
Any author. The signature was made after the certificate had expired or had been revoked.
User is warned that the signature has expired or been revoked. User is prompted to enable or disable macros.
Low
When security it set to low, all macros are treated equally regardless of origin or certificate status. With low security, you receive no prompt or signature validation and macros are automatically enabled. Use this setting only if you are certain that all macros in your files are from trusted sources.
About digital signatures
Microsoft Office XP uses Microsoft Authenticode technology to enable you to digitally sign a file or a macro project. The certificate used to create this signature confirms that the macro or document originated from the signer, and the signature confirms that it has not been altered. When you set the macro security level, you can run macros based on whether they are digitally signed by a developer on your list of trusted sources.
After you have installed your digital certificate, you can sign files and macro projects.
Signing macros
You should sign macros only after your solution has been tested and is ready for distribution, because whenever code in a signed macro project is modified in any way, its digital signature is removed. However, if you have the proper digital certificate on your computer, the macro project will automatically be re-signed when saved. If you want to prevent users of your solution from accidentally modifying your macro project and invalidating your signature, lock the macro project before signing it. Your digital signature says only that you guarantee that this project is safe. It does not prove that you wrote the project. So locking your macro project doesn't prevent another user from replacing the digital signature with another signature. Corporate administrators might re-sign templates and add-ins so that they can control exactly what users may run on their computers.
If you create an add-in that adds code to a macro project, your code should determine if the project is digitally signed and notify the user of the consequences of modifying a signed project before continuing.
Where to get certificates
