Re: Using a resource pool with a Master project
- From: Rob Schneider <rmschne@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Oct 2009 08:58:40 +0000
I've found that, from Project's perspective, the files should always have exactly the same file name all the time. It my be superstition and I cannot "prove" it works (since it requires proving the negative case of no corruption), but it seems to work to avoid file corruption issues related to linked subproject and resource file.
Remember that Project stores the entire full path for linked files. therefore avoid situations where file full path will change, depending on the state of the computer connecting to the source of the files (file server, SharePoint, local drive, etc.)
For example, a file on a file server could be:
Mapped Drive: L:\projects\projectA\mpp\example.mpp
UNC File: \\servername\\sharename\projects\projectA\mpp\example.mpp
In the above example the exact same file can look to Project as being different. There are reports that when Project sees linked file name changes then it leads to corruption.
So I try to ensure all files *look* to Project as being exactly the same all the time by doing things like:
: Create a "standard" on the c: drive for all project files, e.g. c:\projects\projectA\mpp\ for all mpp files for Project A.
: Put copies of those file onto a file server for backup and for others on team to use (if appropriate)
: if others on team use, then they are required to *copy* the files down from the File Server to their own c:\projects\projectA\mpp folder.
: all files for the project go there: shared resource files, subproject files, master files.
Do not copy from source mpp files on file server into the person's private profile space, e.g. in a folder under "My Documents". This is because these full path names are different for each user, e.g. for me on this XP machine it is C:\Documents and Settings\Rmschne\My Documents\projects\projectA\mpp. note "rmschne", my login id, in the path name. This will be different for each person and that will, I think, confuse Project.
In larger team environments, I setup a library in SharePoint (or some other collaboration tool that can do file version management). We check out, then copy the files into to the designated space on the c: drive for working on them. Then when done upload and check in. This approach provides easy versions control for going back, file backups, etc. Even better use a tool like Colligo to automate this file synchronisation between SharePoint and the c: drive.
But at this point, I probably am going over the top in explaining it. The basic thing is to keep it simple by making sure that Project always sees all filenames it has linked to be always unchanging. That is possible with the above "protocol" of finding an place where the file neame never changes and use it for everyone.
--rms
www.rmschneider.com
EL MOVE wrote:
Hi Rob,.
Could you explain deeper what is that "protocol" you use to make project think that files doesn't have been moved?
Thank you so much
Best Regards
Ruben
"Rob Schneider" wrote:
I also find by using a protocol which keeps the files in exactly the same place (from Project's perspective) works (knock on wood) to avoid corruption problems. Make Project *think* "no change" in file name, versions, etc.
--rms
www.rmschneider.com
Rod Gill wrote:Actually it may not be just one time. With 100 files corruption will happen, so code to unattach each file and separate code to then re-attach to a new Resource Pool will be useful. If a re-organization of Files and folders is needed, much, much safer to unattach all files first, then move files and folders etc then re-attach to a new pool.
I've even used a macro to temporarily create a pool for reporting and resource leveling purposes then unattach afterwards to allow PMs to safely take files away to clients, sites etc.
- References:
- Re: Using a resource pool with a Master project
- From: EL MOVE
- Re: Using a resource pool with a Master project
- Prev by Date: Re: Using Priority to Level a Project
- Next by Date: Re: Resource Pool ERROR. Repeated Resources.
- Previous by thread: Re: Using a resource pool with a Master project
- Index(es):
Relevant Pages
|
