Folks...

I need to protect my code for a commercial app I'm designing, so I decided
to (finally) plunge into the world of com-addins

I've spend a week experimenting and learned a lot... BUT...

I need a serious book where COMaddin is not just 1 chapter focused on the
VBIDE. (Getz VBA Dev Handbook)

I need some in-depth stuff... so what's recommended?


I've got both XPdeveloper and VisualBasic 6. I prefer NOT to use .NET so
I can continue to write my VBA without the extra learning curve of VBnet
or C++.


tia,

keepITcool

< email : keepitcool chello nl (with @ and .)
< homepage: http://members.chello.nl/keepitcool

I've never really seen much value in using COM add-ins. The only thing
they're really good for is when you need to run *exactly* the same program
across multiple Office applications, and that's a pretty rare requirement.

It's also very handy to have worksheets available in an add-in for
table-driven command bar building, intermediate calculation areas and other
things that you don't care if the user sees. You don't get worksheets with
COM add-ins. My advice is to put your sensitive code into a VB6 ActiveX DLL
and call the DLL from your add-in. I build lots of commercial-grade
applications this way and it works very well.

--
Rob Bovey, MCSE, MCSD, Excel MVP
Application Professionals
http://www.appspro.com/

* Please post all replies to this newsgroup *
* I delete all unsolicited e-mail responses *


"keepITcool" wrote in message
...
Folks...

I need to protect my code for a commercial app I'm designing, so I decided
to (finally) plunge into the world of com-addins

I've spend a week experimenting and learned a lot... BUT...

I need a serious book where COMaddin is not just 1 chapter focused on the
VBIDE. (Getz VBA Dev Handbook)

I need some in-depth stuff... so what's recommended?


I've got both XPdeveloper and VisualBasic 6. I prefer NOT to use .NET so
I can continue to write my VBA without the extra learning curve of VBnet
or C++.


tia,

keepITcool

< email : keepitcool chello nl (with @ and .)
< homepage: http://members.chello.nl/keepitcool

Rob, great idea.

keeps it simple too... :)


keepITcool

< email : keepitcool chello nl (with @ and .)
< homepage: http://members.chello.nl/keepitcool


"Rob Bovey" wrote:


I've never really seen much value in using COM add-ins. The only
thing
they're really good for is when you need to run *exactly* the same
program across multiple Office applications, and that's a pretty rare
requirement.

It's also very handy to have worksheets available in an add-in for
table-driven command bar building, intermediate calculation areas and
other things that you don't care if the user sees. You don't get
worksheets with COM add-ins. My advice is to put your sensitive code
into a VB6 ActiveX DLL and call the DLL from your add-in. I build lots
of commercial-grade applications this way and it works very well.

I'm interested in this. Any pointers for a newbie to VB6
ActiveX DLL's. Eg creating, register, and how to call from
an addin.

Also am I right in assuming can work in XL97 with if the
vb6 runtime files are installed.

TIA,
Sandy


-----Original Message-----

I've never really seen much value in using COM add-
ins. The only thing
they're really good for is when you need to run *exactly*
the same program
across multiple Office applications, and that's a pretty
rare requirement.

It's also very handy to have worksheets available in
an add-in for
table-driven command bar building, intermediate
calculation areas and other
things that you don't care if the user sees. You don't
get worksheets with
COM add-ins. My advice is to put your sensitive code into
a VB6 ActiveX DLL
and call the DLL from your add-in. I build lots of
commercial-grade
applications this way and it works very well.

--
Rob Bovey, MCSE, MCSD, Excel MVP
Application Professionals
http://www.appspro.com/

* Please post all replies to this newsgroup *
* I delete all unsolicited e-mail responses *


<snip