R
Rod Gill
You have another potential problem. The schedule is inserted linked to the
master? If it is and you edit the path in the master but don't also change
the sub-project, it's a matter of luck and time before one or both projects
corrupt. With any linked scenario the ONLY safe way to edit a link is to
have all affected files open, make the changes then save ALL of them. DDE is
the technology used and it's notoriously flaky.
Personally I find that keeping master projects with links and resource pools
is unreliable and limiting. I always create my consolidated projects and
pools using macros, then once all work has been done, I save, unlink and
save again. This leaves any schedule available to be linked to any master or
resource pool anyone needs.
For reporting purposes I recommend creating a consolidated project with no
links and keeping it for a weekly audit trail. This consolidated project is
then freely available for reporting purposes and also consolidates work for
each resource across all inserted projects which is useful.
I think a design review is maybe worthwhile to focus on what is most
important for this system, then look again at how you are doing things
because this problem you are having is not one that has caused issues before
and between us, we've written hundreds of macro driven systems.
master? If it is and you edit the path in the master but don't also change
the sub-project, it's a matter of luck and time before one or both projects
corrupt. With any linked scenario the ONLY safe way to edit a link is to
have all affected files open, make the changes then save ALL of them. DDE is
the technology used and it's notoriously flaky.
Personally I find that keeping master projects with links and resource pools
is unreliable and limiting. I always create my consolidated projects and
pools using macros, then once all work has been done, I save, unlink and
save again. This leaves any schedule available to be linked to any master or
resource pool anyone needs.
For reporting purposes I recommend creating a consolidated project with no
links and keeping it for a weekly audit trail. This consolidated project is
then freely available for reporting purposes and also consolidates work for
each resource across all inserted projects which is useful.
I think a design review is maybe worthwhile to focus on what is most
important for this system, then look again at how you are doing things
because this problem you are having is not one that has caused issues before
and between us, we've written hundreds of macro driven systems.