Resource Pool: MSP wants to & does open multiple simultaneous copi

[adidistyle]

Hello all. I hope someone can throw some light on this: using MSP2007 Std
SP2 MSP wants to (and does) open multiple simultaneous copies of my Resource
Pool.

I model our production system using 15-30 individual (child) projects
(files) calling on one resource pool for all resources. I insert all these
files into in one master (parent) schedule, also sharing the Resource Pool.
When starting MSP I always open my Resource File first, then open the parent
or child projects as required. The problem arises that sometimes when opening
the individual files or the master schedule, or when expanding projects in
the master MSP will open the Resource Pool again (it shows as a new Window,
which might be different to the one already open).

This can result in the same tasks being assigned to a resource more than
once which is an obvious problem. I cant seem to stop this happening, despite
rebuilding:

1. Removing all child projects from the parent schedule, then unlinking it
from the Resource Pool
2. Stop each child project sharing resources
3. Unlinking all my child projects from the resource pool
4. Renaming resource pool
5. Resharing child projects to new pool
6. Create a new master schedule and insert child projects into that
7. Set new parent schedule to use resources from the resource pool (even
though there a no "tasks" in the parent: it is a collection of inserted
projects that are already sharing from the Pool)

The problem is reduced, but not eliminated. What else can I try? I
definitely only have one Resource Pool file across my entire network. I
thought maybe MSP was getting confused because the files location might have
been defined by mapped drive n: or full UNC address, but I think I have
changed all to UNC now. The problem is not removed by unsharing then
resharing.

I am trying not to touch the resource file as it will a nuisance to rebuild.

 

[Rod Gill]

Hi,

If you or your PMs have ever renamed, moved or over-written any of the
project files, the resource pool or the Consolidated file, then you have
rolled the file corruption dice. One or more files will corrupt sooner or
later if you have done one of the above (It's when not if). Has this ever
been done?

--

Rod Gill
Microsoft MVP for Project

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

 

[adidistyle]

Gulp. I have done all of the above. Numerous times. But not anybody who is
working from a template file be in same position?

The problem does not seem to arise immediately. Anyway I will tread with
caution. After my rebuild procedure I seem to be left with only one problem
child, so I will recreate that from scratch and see how it goes.

Thanks for your input Rod

 

[Rod Gill]

Templates should not be linked to consolidated masters or the resource pool.
Links are all done using the old DDE technology. This is where the
corruption risk comes from.

--

Rod Gill
Microsoft MVP for Project

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