MVPs any ideas on projectbeforetaskchange event issue?

[Mike Thomas]

I have some code in a projectbeforetaskchange event, which produces
odd results under MSp Project 2003.

On a small test plan, I outdent task 16 which is outline level 4, no
subtasks.

On MSP 2000;
the projectbeforetaskchange event does not happen
this seems OK, as the help states it won't fire for changes to outline
number or level

on MSP2002 with the same code & .mpp I get the following events;
Change Task = 16 Field = TaskOutlineLevel NewVal = 3
Change Task = 15 Field = TaskFlag19 NewVal = True (this change is
done by my code triggered by the first event)
again this seems OK, although the help states I shouldn't get an event
from a change in outline level/number - but I can live with this

on MSP2003 with the same code & .mpp I get the following events;
Change Task = 16 Field = pjTaskOutlineLevel NewVal = 3
Change Task = 15 Field = pjTaskFlag19 NewVal = True
Change Task = 15 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 15 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 16 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 16 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 1 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 1 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 0 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 0 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 16 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 16 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 16 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 16 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 6 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 1 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 1 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 1 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 1 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h
Change Task = 0 Field = pjTaskActualWorkProtected NewVal = 0h
Change Task = 0 Field = pjTaskActualOvertimeWorkProtected NewVal = 0h

Task 15 was the immediate parent of task 16, which became a peer when
task 16 was outdented
Tasks 6,1 and ultimately 0 (the Project Summary Task) are the outline
level 2,1 & 0 parents of tasks 15 & 16 after the outdent.
The work protected properties are new in MSP2003.

Any ideas?