Re: Best package to make COM add-in
From: RB Smissaert (bartsmissaert_at_blueyonder.co.uk)
Date: 04/01/04
- Next message: R. Craw: "Repost: cut/paste excel cells w/ ActiveX checkboxes to Word"
- Previous message: Bob Phillips: "Re: Excel - Double Negatives (Past, Present and Future)"
- In reply to: Chip Pearson: "Re: Best package to make COM add-in"
- Next in thread: Howard Kaikow: "Re: Best package to make COM add-in"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 1 Apr 2004 15:54:30 +0100
Thanks.
Will probably opt for Office Developer then. I understand there is no such
thing for
Office 2003, so it will have to be Office Developer XP. I understand that
this is still
available.
RBS
"Chip Pearson" <chip@cpearson.com> wrote in message
news:OoC0p8%23FEHA.3288@TK2MSFTNGP12.phx.gbl...
> That is true. As far as I know, you can't import existing VBA
> userforms in to VB6; therefore, Office Developer would have that
> advantage for converting existing XLA projects to VBA Projects.
>
>
> --
> Cordially,
> Chip Pearson
> Microsoft MVP - Excel
> Pearson Software Consulting, LLC
> www.cpearson.com
>
>
>
> "RB Smissaert" <bartsmissaert@blueyonder.co.uk> wrote in message
> news:%23doY$v%23FEHA.2208@TK2MSFTNGP09.phx.gbl...
> > Thanks. To make it 100% clear then:
> > This is something that can't be done with VB6, so Office
> Developer would
> > have the advantage there.
> >
> > RBS
> >
> > "Chip Pearson" <chip@cpearson.com> wrote in message
> > news:Ok2LVk9FEHA.1720@tk2msftngp13.phx.gbl...
> > > Yes, you can import VBA userforms from an XLA project to a
> VBA
> > > Project. Just drag the form from one project to the other.
> > >
> > >
> > > --
> > > Cordially,
> > > Chip Pearson
> > > Microsoft MVP - Excel
> > > Pearson Software Consulting, LLC
> > > www.cpearson.com
> > >
> > >
> > >
> > >
> > > "RB Smissaert" <bartsmissaert@blueyonder.co.uk> wrote in
> message
> > > news:%236FYgn7FEHA.696@TK2MSFTNGP12.phx.gbl...
> > > > OK, I can see the advantages of VB6 now for future
> projects,
> > > but with a
> > > > large existing add-in to convert with several VBA userforms
> I
> > > presume using
> > > > Office Developer would be easier.
> > > > Is it true that the VBA userforms (from Excel) can be used
> > > directly in
> > > > Office Developer to make the COM add-in?
> > > >
> > > > RBS
> > > >
> > > >
> > > > "Howard Kaikow" <kaikow@standards.com> wrote in message
> > > > news:%23Z2e%2315FEHA.1156@TK2MSFTNGP12.phx.gbl...
> > > > > Using VBA Userforms or VB Forms depends on what you want
> to
> > > do.
> > > > > I prefer VB Forms because those can be directly import
> into
> > > VB .NET and
> > > > > converted to Windows Forms in .NET.
> > > > > It is possible/likely(?) that MSFT may provide a future
> tool
> > > for
> > > > converting
> > > > > VBA Userforms to .NET Windoze Forms, but that's just a
> guess.
> > > > >
> > > > > Using VB, instead of VBA, also allows one to use some
> > > features of VB 6
> > > > that
> > > > > are not available in VBA for Office 97, so one can more
> > > easily code for
> > > > ALL
> > > > > windows versions of Office.
> > > > >
> > > > > For example, see
> > > > >
> > > >
> > >
> >
>
http://www.standards.com/Sorting/SortPerformanceComparison-Description.html.
> > > > > which describes a VB 6 .exe that uses both Excel and Word
> in
> > > Office 97 and
> > > > > up.
> > > > > --
> > > > > http://www.standards.com/; See Howard Kaikow's web site.
> > > > > "RB Smissaert" <bartsmissaert@blueyonder.co.uk> wrote in
> > > message
> > > > > news:ud21ix2FEHA.3912@TK2MSFTNGP10.phx.gbl...
> > > > > > OK, one more in favour of VB6.
> > > > > > Any arguments for this?
> > > > > > How about my question about the userforms and if
> working
> > > with Office
> > > > > > Developer
> > > > > > generally would be easier?
> > > > > >
> > > > > > RBS
> > > > > >
> > > > > >
> > > > > > "Howard Kaikow" <kaikow@standards.com> wrote in message
> > > > > > news:u$1Bln2FEHA.3908@TK2MSFTNGP12.phx.gbl...
> > > > > > > I agree that VB 6 is best.
> > > > > > >
> > > > > > > VSTO only works with Office 2003.
> > > > > > >
> > > > > > > --
> > > > > > > http://www.standards.com/; See Howard Kaikow's web
> site.
> > > > > > > "Chip Pearson" <chip@cpearson.com> wrote in message
> > > > > > > news:Okk9SyzFEHA.3764@TK2MSFTNGP12.phx.gbl...
> > > > > > > > The Visual Studio Tools For Office requires that
> you
> > > have Visual
> > > > > > > > Studio 2003 installed. For writing COM Add-Ins, VB6
> is
> > > best (you
> > > > > > > > can do it in VBNET, but this would require that you
> > > distribute
> > > > > > > > the NET runtime -- about 20MB -- to each user), but
> > > Office XP
> > > > > > > > Developer will do the job.
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Cordially,
> > > > > > > > Chip Pearson
> > > > > > > > Microsoft MVP - Excel
> > > > > > > > Pearson Software Consulting, LLC
> > > > > > > > www.cpearson.com
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > "RB Smissaert" <bartsmissaert@blueyonder.co.uk>
> wrote
> > > in message
> > > > > > > > news:ONPq8%23yFEHA.1180@TK2MSFTNGP09.phx.gbl...
> > > > > > > > > Trying to figure out what the best way is to make
> a
> > > COM add-in.
> > > > > > > > It only will
> > > > > > > > > have to work with Excel.
> > > > > > > > > I understand you will need either VB6 (or one of
> the
> > > other
> > > > > > > > types of VB) or
> > > > > > > > > Office Developer for this.
> > > > > > > > > I would like to make a COM add-in based on a .xla
> > > add-in that
> > > > > > > > has already
> > > > > > > > > been developed.
> > > > > > > > >
> > > > > > > > > Now I am not sure if this is true, but I
> understand
> > > that this
> > > > > > > > would be
> > > > > > > > > easier to do with Office Developer.
> > > > > > > > > I understand that Office Developer XP is still
> > > available and
> > > > > > > > that this will
> > > > > > > > > cost around £330, but there is now
> > > > > > > > > also something called Visual Studio Tools for
> Office
> > > 2003. I
> > > > > > > > work in Office
> > > > > > > > > 2003. Would this be the package to go for (Visual
> > > Studio Tools
> > > > > > > > for Office
> > > > > > > > > 2003) or would Office XP Developer be fine? Then
> > > again if I
> > > > > > > > would go with
> > > > > > > > > Office XP Developer could I keep using Office
> 2003?
> > > > > > > > >
> > > > > > > > > Quite a few confusing issues and I would be
> greatful
> > > for any
> > > > > > > > advice.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > RBS
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>
- Next message: R. Craw: "Repost: cut/paste excel cells w/ ActiveX checkboxes to Word"
- Previous message: Bob Phillips: "Re: Excel - Double Negatives (Past, Present and Future)"
- In reply to: Chip Pearson: "Re: Best package to make COM add-in"
- Next in thread: Howard Kaikow: "Re: Best package to make COM add-in"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
