powerpoint 2002 add-in problem

[Thierry]

We have written an add-in for PowerPoint 2000 (and up) that should
work on all PPT versions, as long as the user has Windows 2000 or
upper OS.

The add-in records your voice in MP3, transforms the ppt into Flash,
and outputs a Flash presentation synchronized with your voice. It
appears as a "Speechi" menu when running PowerPoint.

Works beautifully but some (not all) users seem to have a pb running
PPT2002 + Windows XP. The add-in just does not load, either
automatically (as should be) or manually.

This does not seem to be a security issue (Tools -> Macro -> Security)
since users can play other plug-ins.

Would any body have an idea or even a clue ? Our pb is that the
problem seems to be rare and we can't reproduce the issue internally
so even someone who would reproduce the issue would help us.

To downlaod the plug-in, go to www.speechi.net and then
http://www.speechi.net/speechi/site/speechidemo/setup.exe (English and
French version)

Thanks a lot if you can help,
Thierry
(e-mail address removed)

 

[Steve Rindsberg, PPTMVP]

Works beautifully but some (not all) users seem to have a pb running

PPT2002 + Windows XP. The add-in just does not load, either
automatically (as should be) or manually.

A corrupt user profile seems able to cause this sort of thing. A few of our
users have run into problems where addins just wouldn't install properly or
wouldn't run once installed.

Creating a new profile seems to have solved the problem in many cases.

 

[Shyam Pillai]

I think he is using a COM add-in. Can't say which looking at what he is
referencing and how in the code.

Regards
Shyam Pillai

 

[Thierry]

Thanks a lot for your help. It has been solved and I think the
solution is worth mentioning. We work with developers in France and in
the US. The build was actually produced alternatively in France and in
the US, with the initial build originally done in the US.
When we build with a french version of VB,msvbvm60.dll needs the
library vb6fr.dll to be there (and this is not necessary when we
compile with a US version of VB). So, in summary:
- all machines with vb6fr.dll installed would work
- all versions built in the US would work, whether vb6fr.dll was there
or not
- only the french "builds" working on machine without vb6fr.dll would
not work...
-> that's why it was so rare and hard to circumvent.