Okay Ken I found the issue that was causing the problem and it was deleteing
an inspector in the close event.

The programmer added the inspector to a User Property by doing the following.

NewInspector.CurrentItem.UserProperties.Add("EPIns pectorIndex",
olNumber).Value = m_LastInspector

Then in the close event buried deep in the code I found the following.

Set oUserProp =
m_oInspector001.CurrentItem.UserProperties.Find("E PInspectorIndex")
If Not (oUserProp Is Nothing) Then oUserProp.Delete

This was truly a bizaar problem. Why does this not show up on development
machines? Do you have any idea?



"Ken Slovak - [MVP - Outlook]" wrote:

PMFJI but is your non-Redemption code calling to close either the email item
or the Inspector in either object's Close event? That became an error in a
recent Outlook security update. It's also an error in Outlook 2007.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Tom at GSD" wrote in message
...
You understand correctly. This problem is bizaar. ;-)

Yes the redemption DLL is loaded.

Our customer tells us that this just started happening a couple weeks ago
after new Microsoft security updates were installed.

I am not really a VB programmer but I am going to try a couple other
experiments this morning. I am about at the stage to start commenting out
code and see if the problem goes away.