dynamic link of masterproject to subprojects

[asdasdasdasd123]

Hi,

i created a masterproject with several subprojects. Unfortunaltey, my
collegues have the habit to change the ending of their MSP-filenames
(just the ending) with the date of the last editing. Therefore, all my
links get lost.

I tryed to add a "*" at the end of the file to make the name dynamic.
This even works, but jut the first time, then the "*" gets automatically
replaced through the new ending. Do you know a way to make it dynamic
for all the name and not just the first time?

thx a lot, rgds manu

 

[Rob Schneider]

Sorry, won't work. Your colleagues should stop doing this. If they
don't have a version control system to put these files into (which will
pretty much automate the versioning for them), then they should take
copies of their files and put them into a different folder. These
backups can take on whatever file naming convention they want.

The alternative is that you move all the "source" master and subproject
files somewhere else that only you have access to. You control the
in/out of files to your colleagues and if they return them to you with
different file names, then you rename them.

To avoid file corruption on master/subproject files, a best practice is
to ensure file names don't change.

--rms

www.rmschneider.com

 

[Rod Gill]

Rob's quite correct. I prefer creating new master files each week as
snapshots, so I insert with the link option deselected. This also
consolidates all Resource information. A simple recorded macro makes this
process very quick and easy. Tip: make sure the first recorded action is
File, New

--

Rod Gill
Microsoft MVP for Project - http://www.project-systems.co.nz

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

Sorry, won't work. Your colleagues should stop doing this. If they don't
have a version control system to put these files into (which will pretty
much automate the versioning for them), then they should take copies of
their files and put them into a different folder. These backups can take
on whatever file naming convention they want.

The alternative is that you move all the "source" master and subproject
files somewhere else that only you have access to. You control the in/out
of files to your colleagues and if they return them to you with different
file names, then you rename them.

To avoid file corruption on master/subproject files, a best practice is to
ensure file names don't change.

--rms

www.rmschneider.com






__________ Information from ESET Smart Security, version of virus
signature database 4786 (20100119) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature database 4786 (20100119) __________

The message was checked by ESET Smart Security.

http://www.eset.com