Need Event for task moved:

P

Perticai

I am making a macro where I need to have an event for each task that have
been moved – because I need to check if it is legal to move the task (from a
set of policies) and if it is not legal to move I have to move the task back.
Do any one know what event there can be used for giving an event for each
task that have been moved?

App_ProjectBeforeTaskChange event can not be used because it gives an event
for each task (not only for the moved tasks) in the project for field
188744819 and 188744820 witch are the same events that occur by delete. So I
do not know if it is a move or delete and witch tasks there actually is
affected by the move.

Thanks in advance
Jan Perticai
 
J

John

Perticai said:
I am making a macro where I need to have an event for each task that have
been moved – because I need to check if it is legal to move the task (from a
set of policies) and if it is not legal to move I have to move the task back.
Do any one know what event there can be used for giving an event for each
task that have been moved?

App_ProjectBeforeTaskChange event can not be used because it gives an event
for each task (not only for the moved tasks) in the project for field
188744819 and 188744820 witch are the same events that occur by delete. So I
do not know if it is a move or delete and witch tasks there actually is
affected by the move.

Thanks in advance
Jan Perticai
Click to expand...

Perticai,
It may or may not be easy to create a macro to check for moved tasks,
however I suggest a different approach. First, you mention a set of
policies. That implies your company has a set of rules that should be
followed by users. Well, train the users on those rules and instill in
them a need to follow them. As a backup you can do audits to make sure
users are complying. The best method I found was to do a comparison of
Project files using a before and after approach. Project 2000 and up
either has an add-in or utility called "Compare Project Versions". With
it, two related files (e.g. last week's versions compared to this week's
version) can be directly compared and changes will be noted.

At our company we used a two prong approach. We thoroughly trained all
our users and we also employed a compare macro for both a historical
record of valid changes and to detect unauthorized or inadvertent
changes.

Hope this helps.
John
Project MVP
 
Top