Thank you for taking the time to read this thread.

I just finished building an Excel workbook (.xlsb) containing 4 worksheets, each of which have at least one command button to trigger various VBA modules. The VBA code is not used to define functions, it is code used to automate an Excel process (nothing to do with functions). I want to distribute this workbook as a COM add-in, not a .xla add-in because I want the extra security that a COM add-in offers (an XLA add-in is very weak, see WARNING at bottom of cpearson link 2 lines down). Maybe I should ask a simpler question, since protecting code with a project password is so weak, what is a better way? (maybe there is a better/simpler way than using a COM add-in?)




I have searched this forum and the internet for a good article explaining how to do this, I found several hits dealing with XLA add-in's (this site is excellent: http://www.cpearson.com/excel/createaddin.aspx ) but I could not find a comperable site for COM add-ins for Office 2007.

Would someone please point me to a good article explaining step by step how to do this. For example, I notice 'save as' does not include a COM options, there is a .xla option so I am stumped at the very first step.

Also I understand that I probably need to replace the active X buttons I am presently using for menu buttons (that a ThisWorkbook open event sets up and a ThisWorkbook before close event removes) but is there no way I can link these buttons to the COM add-in code modules? Going away from the buttons will change the look and feel of what I have built already, would rather not invest more time to rework this (if possible).

I am assuming that building a COM add-in is a valid task within Office 2007 suite, maybe I am mistaken? I seem to remember I did this once in Office 2003.

Any suggesting would be greatly appreciated.