Outlook crash

I've been using the script debugger to locate the source of a problem where
Outlook either hangs using 99% processor or terminates with "Outlook.exe has
generated errors......etc" It's only happening when I dismiss a reminder

I've got to the point where I can follow the script all the way through and
it reaches the end before Outlook crashes.

What I can't see is the events that occur after Item_Read() and
Item_PropertyChange() have terminated. How can I find out what happens after
my code has apparently completed?

Jeff Mowatt

You would have to do something, interacting with the item, to cause the
other event handlers in your code to fire. Add breakpoints in the script
debugger first.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"Albacrest" <nospam@albacrest.com> wrote in message
news:1082644335.9331.0@lotis.uk.clara.net...
> I've been using the script debugger to locate the source of a problem
where
> Outlook either hangs using 99% processor or terminates with "Outlook.exe
has
> generated errors......etc" It's only happening when I dismiss a reminder
>
> I've got to the point where I can follow the script all the way through
and
> it reaches the end before Outlook crashes.
>
> What I can't see is the events that occur after Item_Read() and
> Item_PropertyChange() have terminated. How can I find out what happens
after
> my code has apparently completed?
>
> Jeff Mowatt
>
>
>
>

Sue,

Thanks, I managed to find out what it was by a process of eliminating code.
Curiously, the error disappeared when I stopped calling the following
function from the PropertyChange event, yet the debugger skipped through it
time after time with no problem.
Maybe something in here is incompatible with dismissing reminders? FWIW it
isn't needed at this point I realise.

Regards,
Jeff Mowatt

function NotOrganizer()
if isempty(organizer) then
NotOrganizer=false
exit function
end if
if isnull(organizer) then
NotOrganizer=false
exit function
end if
if organizer = "" then
NotOrganizer=false
exit function
end if
if session.currentuser = organizer then
NotOrganizer = false
else
NotOrganizer = true
msgbox "User is not the meeting organizer, update denied"
end if
end function






"Sue Mosher [MVP-Outlook]" <suemvp@outlookcode.com> wrote in message
news:uTt9JyHKEHA.1144@TK2MSFTNGP12.phx.gbl...
> You would have to do something, interacting with the item, to cause the
> other event handlers in your code to fire. Add breakpoints in the script
> debugger first.
>
> --
> Sue Mosher, Outlook MVP
> Author of
> Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
>
> "Albacrest" <nospam@albacrest.com> wrote in message
> news:1082644335.9331.0@lotis.uk.clara.net...
> > I've been using the script debugger to locate the source of a problem
> where
> > Outlook either hangs using 99% processor or terminates with "Outlook.exe
> has
> > generated errors......etc" It's only happening when I dismiss a reminder
> >
> > I've got to the point where I can follow the script all the way through
> and
> > it reaches the end before Outlook crashes.
> >
> > What I can't see is the events that occur after Item_Read() and
> > Item_PropertyChange() have terminated. How can I find out what happens
> after
> > my code has apparently completed?
> >
> > Jeff Mowatt
> >
> >
> >
> >
>
>

I wonder if session.currentuser is the problem. That's a security-blocked
object. Anyway, glad you fixed it.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"Albacrest" <nospam@albacrest.com> wrote in message
news:1083067797.10419.0@doris.uk.clara.net...
> Sue,
>
> Thanks, I managed to find out what it was by a process of eliminating
code.
> Curiously, the error disappeared when I stopped calling the following
> function from the PropertyChange event, yet the debugger skipped through
it
> time after time with no problem.
> Maybe something in here is incompatible with dismissing reminders? FWIW it
> isn't needed at this point I realise.
>
> Regards,
> Jeff Mowatt
>
> function NotOrganizer()
> if isempty(organizer) then
> NotOrganizer=false
> exit function
> end if
> if isnull(organizer) then
> NotOrganizer=false
> exit function
> end if
> if organizer = "" then
> NotOrganizer=false
> exit function
> end if
> if session.currentuser = organizer then
> NotOrganizer = false
> else
> NotOrganizer = true
> msgbox "User is not the meeting organizer, update denied"
> end if
> end function
>
>
>
>
>
>
> "Sue Mosher [MVP-Outlook]" <suemvp@outlookcode.com> wrote in message
> news:uTt9JyHKEHA.1144@TK2MSFTNGP12.phx.gbl...
> > You would have to do something, interacting with the item, to cause the
> > other event handlers in your code to fire. Add breakpoints in the script
> > debugger first.
> >
> > --
> > Sue Mosher, Outlook MVP
> > Author of
> > Microsoft Outlook Programming - Jumpstart for
> > Administrators, Power Users, and Developers
> > http://www.outlookcode.com/jumpstart.aspx
> >
> >
> > "Albacrest" <nospam@albacrest.com> wrote in message
> > news:1082644335.9331.0@lotis.uk.clara.net...
> > > I've been using the script debugger to locate the source of a problem
> > where
> > > Outlook either hangs using 99% processor or terminates with
"Outlook.exe
> > has
> > > generated errors......etc" It's only happening when I dismiss a
reminder
> > >
> > > I've got to the point where I can follow the script all the way
through
> > and
> > > it reaches the end before Outlook crashes.
> > >
> > > What I can't see is the events that occur after Item_Read() and
> > > Item_PropertyChange() have terminated. How can I find out what happens
> > after
> > > my code has apparently completed?
> > >
> > > Jeff Mowatt
> > >
> > >
> > >
> > >
> >
> >
>
>