Forcing user to Enable Macros

[bstobart]

I'm new to MS-project macros, but I'm getting pretty good with MS-Excel
macros. A common problem is that, for security reasons, it is not possible
to force a user to select "enable macros". In the Excel world, we have a
workaround, which is to hide all the worksheets (e.g. in the workbook close
event) in such a way that they can't be unhidden (VeryHidden) without a
password. Then unhide them in a workbook open macro. If the user doesn't
enable macros, he/she sees only a "blank" worksheet telling him/her to enable
macros.

Is there an equivalent workaround for MS-Project?

[Assume that I can't force users to set their security settings a Low.
Further assume that the macros in question are imposing on the users a set of
standards that most users would otherwise bypass.]

 

[Rod Gill]

Only way I know is to add a certificate to the macros from the VBE so they
open silently. You can create a certificate for your own use but need a more
formal one for others to use. Your IT team may well have one you can use.

--

Rod Gill
Project MVP

Project VBA Book, for details visit:
http://www.projectvbabook.com

NEW!! Web based VBA training course delivered by me. For details visit:
http://projectservertraining.com/learning/index.aspx

 

[John]

I'm new to MS-project macros, but I'm getting pretty good with MS-Excel
macros. A common problem is that, for security reasons, it is not possible
to force a user to select "enable macros". In the Excel world, we have a
workaround, which is to hide all the worksheets (e.g. in the workbook close
event) in such a way that they can't be unhidden (VeryHidden) without a
password. Then unhide them in a workbook open macro. If the user doesn't
enable macros, he/she sees only a "blank" worksheet telling him/her to enable
macros.

Is there an equivalent workaround for MS-Project?

[Assume that I can't force users to set their security settings a Low.
Further assume that the macros in question are imposing on the users a set of
standards that most users would otherwise bypass.]

bstobart,
I'll add my two cents to Rod's response.

You're right in that you can't "force" anybody to do anything. However
from what you say in your post it sounds like you (or your company)
needs to take a more proactive approach. The best way to handle this
situation is training, training and more training. Users need to
understand why you need them to run your set of macros. They also need
to understand that every process has a set of groundrules. Follow those
rules and life is easier for everybody, including them.

The above assumes that your company has a set of rules and guidelines
for using Project on your programs. If there are no rules or guidelines,
they need to be developed and used. Just make sure those rules are both
consistent with company goals and also make sure that the rules make
sense (user friendly).

John
Project MVP