Gary,
First let me apologize for my tardy reply. Busy, Busy, Busy
With respect to my odd question, although we strive to have an accurate
baseline in terms of task durations, start/ finish dates, anticipated work,
etc, we have several situations where the project is already underway before
the project schedule is finalized. (I know what you're saying in your
head.... it's a slow process to get everyone on board with the whole plan
first, act later philosophy)
Anyway, what happens is there are tasks that are assigned to resources that
are dependent on other tasks getting done. But until the predecessor tasks
are updated, the dates on the successor tasks may be inaccurate, causing
Overdue TAsk reminders to be sent to the resources that are waiting for
predecessor tasks to be completed. Does that make sense?
To avoid this, I had wanted to wait to publish the successor tasks until the
predecessors were complete, thus pushing the schedule forward to reflect a
more accurate representation of the project timeline. But I inadvertently
published the task assignments for the successor tasks.... so these task
owners started receiving reminders. Not wanting my resources to become
"desensitized" to these reminders, I turned them off completely. I thought
of removing the resources from the assignments and then re-adding them. But
since Project automatically generates a notice to the resource saying they
were taken off the task, I decided that would only add to the confusion.
Whew! I'm sorry this explanation is so long.... but I wanted to make sure
you understood our "unique" situation. That said, it sounds like outside of
removing the resources from the task and then re-adding them, an assignment
cannot be "unpublished", yes?
Oh well... I guess I will need to be more careful in the future
Thank you for your help!!! And I'm so glad you approve of my response to
Richard. I was hoping that I didn't say anything that would make the MVPs
cringe
Christina