What are you concerned about, someone seeing the data or someone amending
the code.

If the former, the XLA worksheets are not visible or amendable from Excel,
unless the user changes the IsAddin property. If the latter, project
protection should cover it.

None of this is foolproof, but it does protect from unintentional misuse.
Malicious or malevolent minded souls are another problem and there is not
much you can do to finally protect from this.

--

HTH

RP

"Chuckles123" wrote in message
...

Our software is Excel 2002, SP-2.
I have one .XLS file, and one corresponding .XLA file, containing zero
data in one Worksheet, one Project, and 13 Modules and Procedures.
Each file is stored on my C drive and on a network shared drive. My
objective is to share the macros across the network.

I am concerned about protection on the shared drive: for the .XLS
file, I am aware of VBAProject - Project Propertis, Protection Tab.
For each of the shared files, I will assign read-only attributes. For
the .XLS shared file, am I correct in assuming that Worksheet and
Workbook protection are not going to do anything for me?

Thanks for a response,
Chuckles123


--
Chuckles123
------------------------------------------------------------------------
Chuckles123's Profile:
http://www.excelforum.com/member.php...o&userid=14948
View this thread: http://www.excelforum.com/showthread...hreadid=267128