As long as the users do not change task lines with external links and
as long as they do not change the file name, the users should be able
to replace (overwrite) the "live file" at work with the home modified
version and not adversely affect the links.
<<
YEOW! - I would think that should scare the [breakfast] out of
anyone!!! ;o)
ESPECIALLY with users I was trying to avoid having to use filters/sorts
!!!! :-o)
I find this particularly a problem, because I'm ASSUMING
-) that if
tasks with external links have their task # changed (by inserting /
deleting tasks) that this would throw everything off. During the setup
of the project - when people most needed to take sub-projects home -
they were actively inserting/deleting/arranging their tasks.
After the project is setup - and the major jobs are mainting task
completion etc.. - almost everyone can simply work on the office copy.
Working remotely with the files is an option - although it has other
complications I was trying to avoid.... (not with project). This is
CLEARLY the preffered method.
Ned[/QUOTE]
Ned,
I understand you want your cake and eat it too - everybody does.
Somewhere somebody has to step up to the plate and take a swing. For the
way you want to view and run your project, the users are going to need
to get comfortable with filters and sorting. Sorry, life is tough, and
with Proejct it is even tougher!
With regard to my suggestion of working at home. Obviously we both agree
the remote server approach is the best. And as I said, its been a long
time since I used the other approach. As I recall Project uses the
Unique ID (UID) for establishing OLE links and therefore adding or
deleting task lines, (other than those with the links), in the users
subproject will not effect OLE links. True, there are ways to change
UIDs also but those require techniques that go beyond normal file
editing.
Here's another suggestion now that you mentioned users will really only
be working on their files at home for initial project setup. Don't worry
about links between subprojects until the basic structure is well
defined. If desired, potential links can be annotated in the Notes field
or a spare text field. This information can then be used once the
dynamic master is created. Or, create a static master each day when
users bring in their changes from home. Delete out the old section of
the master that contains user's subprojects and replace with the new
(i.e. re-insert). There are numerous ways to do this but it is difficult
to give more detailed instructions without really being there and seeing
the actual files.
Just a side note on your comment to Steve's thread this morning. I agree
with Steve. Someone (one person) has got to be ultimately responsible. I
would delegate one of the 2.5 people to be the curator of the master
file. Sharing that responsibility is extremely difficult. No one has the
time to "take the bull by the horns"? Well we both know they will have
all kinds of time to run like heck when "the bull crashes through the
china shop".
I can tell you are having fun.
