J
JohnG@DIB
I have read that we must be sure to set the common resource file as read-only
to protect our common resource information. Is this a task that our tech
resources people must do (they manage all disk/server space) or is there a
way for a user to do this?
Will read-only prevent the updating of assignment information for each
resource to the common resource file from the detail project files?
My main fear (that I have accomplished in testing) is that a user could,
while trying to "clean up" their resource assignments for a specific project,
delete unneeded resources and, thus, also delete those resources from the
common Resource file and ALL other projects that have used the deleted
resource(s).
to protect our common resource information. Is this a task that our tech
resources people must do (they manage all disk/server space) or is there a
way for a user to do this?
Will read-only prevent the updating of assignment information for each
resource to the common resource file from the detail project files?
My main fear (that I have accomplished in testing) is that a user could,
while trying to "clean up" their resource assignments for a specific project,
delete unneeded resources and, thus, also delete those resources from the
common Resource file and ALL other projects that have used the deleted
resource(s).