Enterprise Resource Data for different PMs

[Mel]

We have an unusual, somewhat rare occurrence in MSPS 2007. A project
manager has a resource on their schedule that has had their record
recently updated. When the PM looks at the Resource Sheet data, the
changes are not displaying. However, when another PM opens the same
schedule and looks at the Resource Sheet, the data appears to be
updated. When the first PM closes and opens the schedule, the data
changes never appear in his view, and when he publishes, any data
associated with the resource is the old data, not the new.

We've seen this in pre-SP2 and post-SP2, but it's sporadic. Also,
when the schedule is opened from different entry points (from the
desktop client on a laptop, or from a Remote Desktop Connection), the
results may or may not be the same.

We think that maybe there is a cached copy of the resource record
(similar to a cached copy of the schedule) that is not being updated
when the PM opens the schedule. Has anyone seen this?

 

[Marc Soester [MVP]]

Mel, this is a strange behaviour and I have not seen this before. Here are a
couple of quesitons:

Are you sure that the Resource is not a local resource but is a global
resource? If the resource really is a global resource, I would clear the MS
Project Cache on the client machine where you have the issue and see if this
rectifies the issue.

If this solves the issue, I would also check that this client machine has
SP2 installed.

Hope this helps

 

[Mel]

Mel, this is a strange behaviour and I have not seen this before. Here are a
couple of quesitons:

Are you sure that the Resource is not a local resource but is a global
resource? If the resource really is a global resource, I would clear the MS
Project Cache on the client machine where you have the issue and see if this
rectifies the issue.

If this solves the issue, I would also check that this client machine has
SP2 installed.

Hope this helps
--
Marc Soester [MVP]http://www.i-pmo.com.au







- Show quoted text -

Marc,

Yes, it is not a local resource, but an Enterprise Resource. The PM
used Build Team from Enterprise and selected the record using the
normal procedure.

And, yes -- the system we've seen it on has SP2 installed.

We will try clearing the cache and see if this fixes the issue.

Thanks for the advice,
mel