Unless you want your add-in to be available to other Office applications,
such as Word, it will be much easier to move code from your .xla add-in to a
VB6 ActiveX dll rather than making a COM add-in in either VB6 or VB Net.
VB Net is a whole different language and a COM add-in is quite a bit
different than a .xla add-in. Moving code from an .xla file to a VB6 ActiveX
dll is extremely easy.

RBS


"ExcelMonkey" wrote in message
...
I am contemplating migrating my VBA Add-in (for Excel) into a more secure
product. I was assuming that I could try to migrate this over to VB 6.0
and
create a COM add-in. I also have been wondering whether or not I can
creat
add-ins in VB.Net. I have come to realise that I am confused by some of
the
terminology I see and need clarification.

1) Is "VBA" - as used in Office products (Excel/Word etc) simply "VB 6.0"?
2) Is "VB Script" simply VBA code as used in VBA in Office?
3) If I purchase "Visual Basic 2005 (Express Edition)" what does this
include: VB 6.0, VB.Net, both? I ask this as when you look at the
products
that are included in Visual Basic Studio, you do not see reference to
.Net.
You see Visual Basic, C++ etc but I am not sure if this is based on the
.Net
framework. And if it is, does this mean that I cannot create regular VB
programs?

Thanks

EM