-
I have a class that derives from CoreEmailClasses, the same one I’ve been playing with, but I’m “enhancing” it to use the R6 QuerySend. This cuts out quite a bit of chafe from QuerySave; a lot less code is required, and less hoop-jumping to ensure data validity.- After making this change it’s not working right, so I ran a Memo send in the debugger, and it shows that in the QuerySave event, the UIMemoDocument::m_noteMemo object does not have a Body field (or Body1, or wBody, or anything body related) on it anywhere!
-
AFTER it calls UIMemoDocument::m_noteUIMemo.Send(), the Body field magically appears. It also appears to compute quite a number of other values, completely whomping all work done by the QuerySend event code, which was of course triggered by that very Send() invocation.
-
It’s never done this before … in QuerySave the expected Items have always been present. I did do a “Recompile All LotusScript” because the enhancment caused a Use Module error on cMemoObject, and recompiling the code heirarchy didn’t fix it. Last time that happened I had to do a “Recompile All LotusScript” and it went away, and it didn’t cause any other flakiness to crop up.
-
Anyone know why would this be happening?