"arno" wrote in message ...

Whatever you do in Office Applications can be hacked by some who knows how
to. We try to hide and protect anything from "normal" users as good as
possible knowing that there's always a way to crack the file, if you have
access to the folder, access to the PC, access to the server, access to the
building.

If the user can *legitimately* open a workbook then they automatically
have legitimate access to the Visual Basic Editor. Do you really think
enumerating a public collection is a hack/crack?

If you want to hide something from a 'normal' user, I'd consider a
hidden Name to be inadequate, for the reason I have given i.e. hidden
Names are still very visible IMO. Putting a password in VBA code and
giving the VBA project a password I *would* consider adequate (but not
ideal). A VBA developer could discover this password but surely no one
would argue that this would not be hacking/cracking.

--