F
Frank Schwab
I have a PowerPoint Com Add-In written in Visual Basic 6.0 SP2, and signed
with a Verisign certificate. All appears well here. However, a number of
customers in the field (as well as our CEO, who unforunately happens to exist
on the other coast) have reported that, after upgrading their Office
2000/Windows XP systems to XP SP2, our Com Add-In stops loading. Of course,
on my machine it works perfectly, even after doing the same upgrade.
The CEO has downgraded back to SP1a, which didn't resolve the problem, as
well as upgrading to Office 2003, which still didn't solve the problem.
We've gone through his registry looking at all of the necessary keys; all
appears to be in order.
The symptoms are a bit infuriating - PowerPoint simply will not load the Com
Add-In. It should auto-load at PP startup, but doesn't. The user can go
through the Com Add-ins button and browse to the .dll file, but PP will not
load it, and shows no error message. I've placed debugging code in the
OnConnection handler which appears to never get executed, leading me to
believe that it's not a failure in my code.
Does anyone have any suggestions as to how I might debug this problem, or
what the problem might be?
Unhappy CEO's are unpleasant people.
/frank
with a Verisign certificate. All appears well here. However, a number of
customers in the field (as well as our CEO, who unforunately happens to exist
on the other coast) have reported that, after upgrading their Office
2000/Windows XP systems to XP SP2, our Com Add-In stops loading. Of course,
on my machine it works perfectly, even after doing the same upgrade.
The CEO has downgraded back to SP1a, which didn't resolve the problem, as
well as upgrading to Office 2003, which still didn't solve the problem.
We've gone through his registry looking at all of the necessary keys; all
appears to be in order.
The symptoms are a bit infuriating - PowerPoint simply will not load the Com
Add-In. It should auto-load at PP startup, but doesn't. The user can go
through the Com Add-ins button and browse to the .dll file, but PP will not
load it, and shows no error message. I've placed debugging code in the
OnConnection handler which appears to never get executed, leading me to
believe that it's not a failure in my code.
Does anyone have any suggestions as to how I might debug this problem, or
what the problem might be?
Unhappy CEO's are unpleasant people.
/frank