Update flag based on field value change

[dbonline]

I have read in previous posts that MS Project does not let you read the font
color. I have users that modify a copy of the project file and change the
font colors for those field values they changed.
I search through the file for these font color changes to review the value
change and then copy into the master project file. I have not been able to
successfully train my users to always set a flag when they change a value in
a task row.
Is there some way to automatically set this flag when a value changes in the
row?

Thanks.

 

[Rod Gill]

There is, but the events have been notoriously picky about what makes them
fire! It will be safer to make this a training issue as you cannot guarantee
that changing any one thing for a task will fire the task change event.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[John]

I have read in previous posts that MS Project does not let you read the font
color. I have users that modify a copy of the project file and change the
font colors for those field values they changed.
I search through the file for these font color changes to review the value
change and then copy into the master project file. I have not been able to
successfully train my users to always set a flag when they change a value in
a task row.
Is there some way to automatically set this flag when a value changes in the
row?

Thanks.

dbonline,
Years ago I wrote a VBA macro that compared two projects and highlighted
with font color all fields that were changed in addition to placing an
annotation mark in a spare field to indicate the type of change (i.e.
addition, deletion, etc.). Basically it does exactly what you want to do.

With the release of Project 2000, Microsoft included a Compare Project
Versions utility as part of the Analysis toolbar. The utility doesn't
color code the changes like my macro, but it does create a change file,
and that should give you what you need. Give it a try. Again, the
utility doesn't require users to make an special effort for changes.

Hope this helps.

John
Project MVP

 

[dbonline]

John,

Thanks for your reply. I have tried the utility you mentioned, however I
get the following error when run:

Compare Project Versions Utility Run-time error '1101': The argument is not
valid

Error!
An error occured in the COM add-in named: Compare Project Versions
Error #:440 Automation error
Please restart Microsoft Office Project to restart the COM add-in

Even after restart I get the same error. Any ideas?

Thanks.

 

[John]

John,

Thanks for your reply. I have tried the utility you mentioned, however I
get the following error when run:

Compare Project Versions Utility Run-time error '1101': The argument is not
valid

Error!
An error occured in the COM add-in named: Compare Project Versions
Error #:440 Automation error
Please restart Microsoft Office Project to restart the COM add-in

Even after restart I get the same error. Any ideas?

Thanks.

dbonline,
Unfortunately we seem to be seeing several posts citing problems with
the utility over the last few months. As a matter of fact, a poster in
the regular newsgroup, (microsoft.public.project), posted yesterday,
("Compare two Projects in 2003" by Dayle), with a similar problem. I
responded and gave a couple of suggestions. Check the thread on that
post and see if it helps.

John
Project MVP