#7505
RPP
Participant

    Thanks for the replies. The information has proved very useful.

    I removed/replaced the Integrations as described and the simple act of doing so reminded me that one of my applets does fire on the Open event. Doh! Haven’t changed this one in ages though which is why I was ignoring it. I guess it’s always been busted for shared folders (no other folders have caused problems) but it hasn’t been apparent until now.

    The extra information about the Trace facility is very handy, I have been ruing Formativ for a lack of runtime debugging and using message boxes instead – which sometimes ruins the test in itself. I shall get the third party tool at once!

    For this test msgboxes worked fine, the suspect code is as follows

    Dim oMsg
    Dim oAcct

    msgbox “s1”

    Set oAcct = Client.ClientState.CurrentAccount

    msgbox “s2”

    On Error Resume Next
    Set oMsg = Client.ClientState.CommandMessage
    On Error Goto 0
    If Not IsObject(oMsg) Then
    On Error Resume Next
    Set oMsg = oAcct.GetMessage(Groupwise.ItemMessageIDFromView())
    On Error Goto 0
    End If

    msgbox “s3”

    If IsObject(oMsg) Then

    msgbox “s4”

    < code within the loop isn’t relevant at this point >

    End If

    My applet is triggered by the Groupwise application level event of ItemRead

    The event fires twice.

    The first time I get messages for S1, S2, S3 and no error. I don’t get S4 but I know why.

    The second time I get messages for S1, S2 and then the error message.

    A few extra message boxes seems to indicate the problem is with this part of the code …

    On Error Resume Next
    Set oMsg = Client.ClientState.CommandMessage
    On Error Goto 0

    Specifically the “Set oMsg = Client.ClientState.CommandMessage” call

    Am at a bit of a loss in how to code around this. I don’t really want the second call to fire at all, especially since it then crashes!

    This problem only occurs on my PC (where Creator is) and only for emails in Shared folders so I can live with it but I suspect it leads to the Catastrophic Failure message eventually.

    I’ll experiment a little more and see if I can get around it.

    Thanks for your help so far

    Simon