S
Sue Mosher [MVP]
Rereading your posts (which wasn't easy to do -- please quote the relevant
portion of previous posts to keep the conversation in one place), I have to
wonder whether you originally were thinking about implementing this as a
custom form project by having the server change the value of the
MessageClass property for certain items. I wouldn't recommend that, because
unless your server is set to strip TNEF content from outgoing messages,
using a custom message class will cause problems with attachments on any of
these messages that are forwarded to non-Outlook recipients. If that's not
an issue, the relevant events are Read and Open and can be inserted into the
VBScript editor with the Script | Event Handler command.
However, that still doesn't address the issue of what's going to happen to
the original message content, which you said you wanted to preserve.
Sue Mosher
"Sue Mosher [MVP]" <suemvp@turtleflock.com> wrote in message news:...
> Forms published to the Organizational Forms library run VBScript code, not
> VBA code, and would not provide a solution for your scenario.
> These articles on Outlook events include VBA code samples and are also
> available in VBA Help on your machine:
> http://msdn.microsoft.com/en-us/library/bb147654.aspx -
> Explorer.SelectionChange
> http://msdn.microsoft.com/en-us/library/bb147644.aspx -
> Inspectors.NewInspector
> Still looking for an answer to my question about what you plan to do with
> the original message's content if you replace all the fields with data
> from some other source.
> "Duke2" <Duke2> wrote in message
> news:526832FB-2545-42AD-A465-9362D948A631@microsoft.com...
> >I thought by publishing into Organizational Forms Library, I can easily
> > distribute these macros to the users. But after looking at your post, I'm
> > bit
> > worried.
>
>> my intention is not to show the message's original contents if it
> > qualifies
> > my criteria (as I described before). I've also modified OWA premium pages
> > to
> > do the same thing. OWA part is prety much complete, but it appears that
> > without installing anything on client's machine, I wont be able to do the
> > same thing with Outlook.
>
>> If we forget the distribution difficulty for a minute and think this only
> > needs to work on a single Outlook instance, how can I capture the events
> > and
> > call a macro? Can you show me an example of this?
>
>> Thanks
> > Duke
>
>
>
>>
>
portion of previous posts to keep the conversation in one place), I have to
wonder whether you originally were thinking about implementing this as a
custom form project by having the server change the value of the
MessageClass property for certain items. I wouldn't recommend that, because
unless your server is set to strip TNEF content from outgoing messages,
using a custom message class will cause problems with attachments on any of
these messages that are forwarded to non-Outlook recipients. If that's not
an issue, the relevant events are Read and Open and can be inserted into the
VBScript editor with the Script | Event Handler command.
However, that still doesn't address the issue of what's going to happen to
the original message content, which you said you wanted to preserve.
Sue Mosher
"Sue Mosher [MVP]" <suemvp@turtleflock.com> wrote in message news:...
> Forms published to the Organizational Forms library run VBScript code, not
> VBA code, and would not provide a solution for your scenario.
> These articles on Outlook events include VBA code samples and are also
> available in VBA Help on your machine:
> http://msdn.microsoft.com/en-us/library/bb147654.aspx -
> Explorer.SelectionChange
> http://msdn.microsoft.com/en-us/library/bb147644.aspx -
> Inspectors.NewInspector
> Still looking for an answer to my question about what you plan to do with
> the original message's content if you replace all the fields with data
> from some other source.
> "Duke2" <Duke2> wrote in message
> news:526832FB-2545-42AD-A465-9362D948A631@microsoft.com...
> >I thought by publishing into Organizational Forms Library, I can easily
> > distribute these macros to the users. But after looking at your post, I'm
> > bit
> > worried.
>
>> my intention is not to show the message's original contents if it
> > qualifies
> > my criteria (as I described before). I've also modified OWA premium pages
> > to
> > do the same thing. OWA part is prety much complete, but it appears that
> > without installing anything on client's machine, I wont be able to do the
> > same thing with Outlook.
>
>> If we forget the distribution difficulty for a minute and think this only
> > needs to work on a single Outlook instance, how can I capture the events
> > and
> > call a macro? Can you show me an example of this?
>
>> Thanks
> > Duke
>
>
>
>>
>