M
Michael Zino
Dear All,
I am using the Redemption component in an Outlook add-in project, which is
targeted for usage in Outlook Y2K, XP, and 2003.
Lately, I am facing a strange behavior on several workstations while using
my add-in.
I was able to trap the problem using the following code:
LogMsg "Creating MAPIUtils Object."
Set oUtils = Utils.GetSafeItem("Redemption.MAPIUtils")
LogMsg "MAPIUtils Created. Calling oUtils.CreateRecipient."
Set oSafeRecipient = oUtils.CreateRecipient(strResourceName)
LogMsg "After Creating SafeRecipient."
While executing the "oUtils.CreateRecipient" method, I can see that the
workstation's available memory drops dramatically and the time passed before
it returns exceeds any logical period.
Please note that, the strResourceName consists of a valid SMTP address.
I am currently using Redemption 3.3.
Please advice.
Regards,
Michael Zino
I am using the Redemption component in an Outlook add-in project, which is
targeted for usage in Outlook Y2K, XP, and 2003.
Lately, I am facing a strange behavior on several workstations while using
my add-in.
I was able to trap the problem using the following code:
LogMsg "Creating MAPIUtils Object."
Set oUtils = Utils.GetSafeItem("Redemption.MAPIUtils")
LogMsg "MAPIUtils Created. Calling oUtils.CreateRecipient."
Set oSafeRecipient = oUtils.CreateRecipient(strResourceName)
LogMsg "After Creating SafeRecipient."
While executing the "oUtils.CreateRecipient" method, I can see that the
workstation's available memory drops dramatically and the time passed before
it returns exceeds any logical period.
Please note that, the strResourceName consists of a valid SMTP address.
I am currently using Redemption 3.3.
Please advice.
Regards,
Michael Zino