Is COM over? - what are my options?
 

I have written an excel add-in using vba and since I am quite pleased
with the outcome thought I would compile it as a COM add-in to protect
all my hard work (and also maybe make some of the .ocx controls a bit
more robust??). Some recent searches indicate that I need to upgrade
my Office version to the "Developer Edition" to do this (at the moment
I just have XP Pro). As far as I can tell though this upgrade is no
longer available though.

My add-in is <1Mb and I have worked hard to keep it that small so
distributing the .Net framework seems like a real over-kill. What are
my other options? Looking at MSDN it's almost as if vb (classic) and
COM never existed.

Thanks in advance,

Andrew

Is COM over? - what are my options?
 

If you have vb classic, you don't need the developer edition.

the knowledge base
http://support.microsoft.com

should still have articles on creating a COM addin.

--
Regards,
Tom Ogilvy



wrote in message
oups.com...
I have written an excel add-in using vba and since I am quite pleased
with the outcome thought I would compile it as a COM add-in to protect
all my hard work (and also maybe make some of the .ocx controls a bit
more robust??). Some recent searches indicate that I need to upgrade
my Office version to the "Developer Edition" to do this (at the moment
I just have XP Pro). As far as I can tell though this upgrade is no
longer available though.

My add-in is <1Mb and I have worked hard to keep it that small so
distributing the .Net framework seems like a real over-kill. What are
my other options? Looking at MSDN it's almost as if vb (classic) and
COM never existed.

Thanks in advance,

Andrew

Is COM over? - what are my options?
 

Hi Tom,

Thanks for the reply. I don't actuallly have vb classic either
although maybe I have a better chance of finding an old copy for sale.
(So far I've only worked with vba.)

I had read that to move from vba to vb6 would require me to re-create
my forms (which was the reason I was tending towards Dev. Ed.) Do you
know if this is actually the case for COM add-ins or does that comment
only apply if I wanted to create a executable.

Thanks again,
Andrew


Tom Ogilvy wrote:
If you have vb classic, you don't need the developer edition.

the knowledge base
http://support.microsoft.com

should still have articles on creating a COM addin.

--
Regards,
Tom Ogilvy



wrote in message
oups.com...
I have written an excel add-in using vba and since I am quite pleased
with the outcome thought I would compile it as a COM add-in to protect
all my hard work (and also maybe make some of the .ocx controls a bit
more robust??). Some recent searches indicate that I need to upgrade
my Office version to the "Developer Edition" to do this (at the moment
I just have XP Pro). As far as I can tell though this upgrade is no
longer available though.

My add-in is <1Mb and I have worked hard to keep it that small so
distributing the .Net framework seems like a real over-kill. What are
my other options? Looking at MSDN it's almost as if vb (classic) and
COM never existed.

Thanks in advance,

Andrew

Is COM over? - what are my options?
 

I had read that to move from vba to vb6 would require me to re-create
my forms

You would have to recreate your form because VBA and VB6 use different forms
packages. You'll have to do that anyway if you decide to go with .Net. If
you cannot get Office XP Developer you might want to go the .Net route
because it's officially "the future".

--
Jim
wrote in message
ups.com...
| Hi Tom,
|
| Thanks for the reply. I don't actuallly have vb classic either
| although maybe I have a better chance of finding an old copy for sale.
| (So far I've only worked with vba.)
|
| I had read that to move from vba to vb6 would require me to re-create
| my forms (which was the reason I was tending towards Dev. Ed.) Do you
| know if this is actually the case for COM add-ins or does that comment
| only apply if I wanted to create a executable.
|
| Thanks again,
| Andrew
|
|
| Tom Ogilvy wrote:
| If you have vb classic, you don't need the developer edition.
|
| the knowledge base
| http://support.microsoft.com
|
| should still have articles on creating a COM addin.
|
| --
| Regards,
| Tom Ogilvy
|
|
|
| wrote in message
| oups.com...
| I have written an excel add-in using vba and since I am quite pleased
| with the outcome thought I would compile it as a COM add-in to protect
| all my hard work (and also maybe make some of the .ocx controls a bit
| more robust??). Some recent searches indicate that I need to upgrade
| my Office version to the "Developer Edition" to do this (at the moment
| I just have XP Pro). As far as I can tell though this upgrade is no
| longer available though.
|
| My add-in is <1Mb and I have worked hard to keep it that small so
| distributing the .Net framework seems like a real over-kill. What are
| my other options? Looking at MSDN it's almost as if vb (classic) and
| COM never existed.
|
| Thanks in advance,
|
| Andrew
|
|

Is COM over? - what are my options?
 

Hi Jim,

Would you have a feel for what %age of users have arrived at the future and
are in a position to deploy .Net.

Or, how long will the significant or critical mass remain in MS's past, and
continue to require VBA or VB6/COM.

Regards,
Peter T

"Jim Rech" wrote in message
...
I had read that to move from vba to vb6 would require me to re-create
my forms

You would have to recreate your form because VBA and VB6 use different
forms
packages. You'll have to do that anyway if you decide to go with .Net.
If
you cannot get Office XP Developer you might want to go the .Net route
because it's officially "the future".

--
Jim
wrote in message
ups.com...
| Hi Tom,
|
| Thanks for the reply. I don't actuallly have vb classic either
| although maybe I have a better chance of finding an old copy for sale.
| (So far I've only worked with vba.)
|
| I had read that to move from vba to vb6 would require me to re-create
| my forms (which was the reason I was tending towards Dev. Ed.) Do you
| know if this is actually the case for COM add-ins or does that comment
| only apply if I wanted to create a executable.
|
| Thanks again,
| Andrew
|
|
| Tom Ogilvy wrote:
| If you have vb classic, you don't need the developer edition.
|
| the knowledge base
| http://support.microsoft.com
|
| should still have articles on creating a COM addin.
|
| --
| Regards,
| Tom Ogilvy
|
|
|
| wrote in message
| oups.com...
| I have written an excel add-in using vba and since I am quite
pleased
| with the outcome thought I would compile it as a COM add-in to
protect
| all my hard work (and also maybe make some of the .ocx controls a
bit
| more robust??). Some recent searches indicate that I need to
upgrade
| my Office version to the "Developer Edition" to do this (at the
moment
| I just have XP Pro). As far as I can tell though this upgrade is no
| longer available though.
|
| My add-in is <1Mb and I have worked hard to keep it that small so
| distributing the .Net framework seems like a real over-kill. What
are
| my other options? Looking at MSDN it's almost as if vb (classic)
and
| COM never existed.
|
| Thanks in advance,
|
| Andrew
|
|