Security option in programme

Shahul

My preferred method is to distribute reports using Adobe Acrobat or any other PDF writer. This will make the reports available to anyone without the need of the software, just a free PDF viewer. Here you control exactly what they will be able to see.

You can explore netset to see if this gives you the functionality you are looking but I suspect it will not as soon as the file is taken away from the network and accessed from other location even when using Backup files.

Because P3 is becoming somewhat obsolete, and no one I know is investing in P3 I already un-installed P3 from my computer, to me makes no sense using P3 anymore. For this reason I cannot explore netset to see if we can get this functionality you are looking.

A limited option would be to copy the files into a folder, set them under windows explorer as read only and distribute them with the knowledge anyone can set them back as writable files.

Also the Save As function might be a way to fool the protection even when in the network, this also you got to explore. I never used in my computer a network installation for P3.

Best regards,
Rafael

Shahul,

As password protection is not there, and if u want to check the changes done in the program, use CLAIM DIGGER to find out the changes.

Its a utility tool to compare programs. U can check with ur IT / admin guys.

Thanks to all

Raviraj,

Are you aware that Primavera ceased selling Claim Digger for P3 at the beginning of this year?

Hi Mr.Ronald

It means P3 too have claim digger? I thought it is available in P6

P6 includes a free Claim Digger module that only works for P5/P6 schedules. That is still available when you purchase P6.

This is a P3 forum. The Claim Digger module for P3 schedules has always been sold separately, and like P3 is no longer for sale.

Ronald,

Is Digger within P6 equal to Digger for P3 as an external module, or a similar, not so similar? They might be as different as P3 was to P3e.

We gave P6 a try for a few weeks before giving up, we compared two files, a prior period and an update schedule but many fields were marked as different because of a field prefix in the database. We also did not figure out how to compare changes in calendar days/work ours.

Any suggestion will be welcomed so in the future we can deal with the issue; also we are interested in knowing how difficult would be for the other part to figure out our changes, it is good to know the strengths as well as the weakness.

Best regards,
Rafael

Thanks Mr.Rafeal