I know - I feel your pain. The MS written Macro warning is (IMHO) fairly
typically written in language that only the experienced geek like me would
understand; to the typical user it is unintelligible and scary and the
natural tendency is to want to say no, don't let these dangerous things
happen on my computer! I work at a hospital, I develop data analysis tools
that I distribute for nursing directors, etc. to use, and often they are only
used monthly or quarterly - too infrequently for them to remember what the
message means or how to respond. Or (adding to the fun) sometimes our MIS
people will push down something through the network that resets all the Excel
default settings, including setting macro security to high so the prompt
doesn't even show. I just love those calls... "I pushed the button, but
nothing happened! What do I do?" "Well, see your Tools menu... That's up at
the top of the screen. No, up near where it says...."

Hey, gotta vent every now and then! At least you folks will understand!
K Dales

"Jack_Feeman" wrote:

Thanks everyone for the input. It is what I figured. Was just hoping someone
knew how to tap into the macro warning message to amend it to read "by not
selecting OK" the template will not work or similar message. I was trying to
help new users to understand saying no would make the template unusable. So I
will have to display this information in the instructions (who reads them
anyway?) for the template. Thanks again all.
Jack

"Tushar Mehta" wrote:

Hi Tom,

XL2003 will not trust a self-signed certificate on a machine that lacks
the private key for that certificate -- something that should be
present only on the machine that created the certificate.

Only third party certificates (read several hundred $$ each year for
individuals) work.

--
Regards,

Tushar Mehta
www.tushar-mehta.com
Excel, PowerPoint, and VBA add-ins, tutorials
Custom MS Office productivity solutions

In article ,
says...
In xl2000 or later, you would need to certify your project and have the user
accept you as a trusted source.

An alternative would be to put your code in an addin and have the user load
the addin.