Do I understand correctly thar if you do *not*use Redemption at all (i.e.
the button is not clicked and no Redemption object is ever
created/referenced/etc), you get an error. Bu if you click on the button
(and load Redemption), you do *not* get the error.
Sounds like Redemption actually *fixes* the problem rather than causes one
:-)

What happens if you uncheck Redemption from Tools | Options | Other |
Advanced | Add-in manager, then use Process Explorer from sysinternals.com
to see if Redemption.dll is even loaded by the eoutlook.exe process?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tom at GSD" wrote in message
...
I have been requested to look at a VB 6.0 extension that is utilizing the
redemption library. It is rather a simple extension that employs a one
button
command bar. The button simply adds an html item to the existing html
message
in the new message window (HTML only - no word), uses the redemption
library
to modify the some properties and a few other things. Essentially the
active
code in the extension is ONLY utilized when the user adds this HTML via
the
button and will not do anything if the user does not.

So if we create a message without clicking the button to add the HTML and
then send it (no HTML added) we get run-time error on XP SP2 and Vista. My
customer tells me that this just started happening to them after the
latest
volley of security patches in the last few weeks.

Symptom #1: On XP we get the following runtime errors

0xD6A4010A AND 0XBFE4010A
"Method '~' of object '~' failed

On Vista we get

0xEB44010A
"Method '~' of object '~' failed

I set break points in the code and message boxes for the release version
and
we do not hit any of the code within the extension.

Symptom # 2 - The problem does not happen on development machines (Visual
Studio 2003 & Visual Studio 6.0 installed) we do not get any errors at
all.
We have tested this on three development machines. So as far as we can
tell
this only happens on machines that are regular users.

Symptom #3 - The problem does not happen when we send an email with the
HTML
added. This would mean that the redemption library is actively used and
the
button has been depressed meaning the HTML was inserted.

Symptom # 4 - This happens with all versions of the Redemption DLL form
3.4
to 4.3.


Does anyone have any idea what is happening.

Thanks in advance!