Shared Resource Protections

[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).

 

[James G]

Hi John,

Yes, it would normally be an IT Administrator who would have the password to
amend the common resource file.....although it could be anyone you nominate.

Yes, a read-only file will prevent the updating of assignment information
for each resource to that of the common resource file. This solves the
problem of the system speed become slower, and it also stops the problem of
anyone accidentally deleting resource names. However, it also stops you from
seeing the workload for each resource, directly from the common resource
file. In order to see the total workload, you will need to compile a
consolidated project file by inserting all your projects into one master
file....or you could use a Cube.

We had very much the same situation as you describe, and the only way to
ensure the integrity of the resource data was to make it read-only. Ok, it
imposed some limitations, but it certainly solved more problems.

HTH.

James.G