Add-in not listed in Project VBE explorer?

  • Thread starter Thread starter Jen
  • Start date Start date
J

Jen

Hi There,

I recently started to program a tiny little bit in VBA Excel. And I try to
do similary now in PPT.

There are plenty of add-ins around for Excel ... far less for PPT. But I
would expect that they would load in the same way, no?
Eg. every Add-in I load in Excel appears in the "Project VBE explorer".
Similarly i loaded Tushar's PPt-timer add-in... and the add-in works great!
As to be expected with Tushar's work...:)

But while I was trying my first steps in VBA-ppt myself ....I noticed that
Tushar's Add-in wasn't mentioned there.
Curious by nature I am just wondering why (it is different than with
excel)...

Brgds, Jen
 
There are plenty of add-ins around for Excel ... far less for PPT. But I
would expect that they would load in the same way, no?

No. PPT, Word and Excel all handle add-ins and VBA code differently.
Eg. every Add-in I load in Excel appears in the "Project VBE explorer".
Similarly i loaded Tushar's PPt-timer add-in... and the add-in works great!
As to be expected with Tushar's work...:)

But while I was trying my first steps in VBA-ppt myself ....I noticed that
Tushar's Add-in wasn't mentioned there.
Curious by nature I am just wondering why (it is different than with
excel)...

Why? I'd guess that nobody really knows any more. It's been this way since
VBA was introduced in PPT 97.

But have a look here:

http://officeone.mvps.org/vba/howto_get_vba_code_from_addin.html
 
Hi Steve,

Thanks for the insight!
It is a bit strange that there is no "uniformity" ..between the different
MSO-applications, but hey I will not be the one complaining for the
zillionth time (my guess) about this...

I have no intention of getting VBA-code from Tushar's Add-in (it is
protected anyway). I was just wodnering on why the behaviour of for loading
add-ins was different than with Excel for instance.

Thanks, Jen!
 
I have no intention of getting VBA-code from Tushar's Add-in (it is
protected anyway).

Oh, sorry ... I didn't mean to imply that that was what you were after.
But using th same registry setting mentioned in that article allows you to see
loaded add-ins and, if they're your own or at least unprotected, to edit them
in place. It's a FAR faster way to test/fix add-ins than opening the PPT,
saving as PPA, testing, wondering what went wrong, repeat until hair falls out.

With the PPA open, you can set breakpoints, SEE what goes wrong and usually do
a test fix on the spot.

The only hitch is that you can't save the code from the addin, though PPT
pretends to let you do so. Instead, once its' fixed, copy/paste it back into
the source PPT, or export the modules and later import them back into the
source PPT.

I'm babbling again, aren't I?
I was just wodnering on why the behaviour of for loading
add-ins was different than with Excel for instance.

My best guess at an answer:

Because.

;-)
 
Hi Steve,

Thank you for the explanations ... it all seems very developer-
unfriendly!
Hope MS does not get it into their mind to do the same with excel ...

Jen :)
 
Hi Steve,

Thank you for the explanations ... it all seems very developer-
unfriendly!

It's not especially onerous once you get used to it.

Just different.
 
Back
Top