A COM Add-In (CAI) provides no additional protection for existing VBA code.
The security advantage of using a CAI is that you never distribute the
source code to the end users. All that you deploy is a DLL file compiled to
machine code. You can rewrite your existing XLA add-ins as COM Add-Ins and
you can write new add-ins as CAIs, but a CAI has no effect whatsoever on the
security of existing VBA. See www.cpearson.com/Excel/CreatingCOMAddIn.aspx
for VB6 code COM Add-Ins. If you just want to add new functions, you can use
an Automation Add-In, which is a slimmed down COM Add-Ins. See
www.cpearson.com/Excel/AutomationAddIns.aspx . For creating a function
library in NET, see http://www.cpearson.com/Excel/Creati...nctionLib.aspx.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)

"Peter Ostermann" wrote in message
...
Hi NG,

question especially MVPs:
The protection for VBA code in Excel application is notoriously week. It
is said, that only a com-addin could help. For MS it is or would have been
easy to supply such an addin. Where could it be found?

Regards
Peter Ostermann