Yes there is but it would be classed as "virus" activity if you use it
to change someone elses settings. What you should do is password protect
your project first before distributing it, this is then your choice and
not manipulating the choices of others, i can see no valid reason to
lock a vba project after it is distributed!


--
The Code Cage Team

Regards,
The Code Cage Team
------------------------------------------------------------------------
The Code Cage Team's Profile: http://www.thecodecage.com/forumz/member.php?userid=2
View this thread: http://www.thecodecage.com/forumz/showthread.php?t=6604