read-only file

[Hope]

Bye to all,

I have a generic in creo3 that I would like to make unchangeable (we do not have a plm).
If I put it in a single reading, it still allows me to create instances. Do you have any idea how I can do this?

alternatively I would also try from windows but every time save the part creates a new rescue.
The only thing that came to mind is to put the file in a folder and put that in read-only.

every board is well accepted.

 

[Hope]

this interesting solution I found on a ptc forum.

creo has a maximum number of incremental rescues (32767).
if you open the part prt001.prt.32767 and you save, you create the part prt001.prt.-32768
this is not perceived as part "valid" (due to the hyphen) by creo that then continues to open version 32767.

Therefore, if I save my generic and imposed the increase to 32767 no one will ever be able to change it (unless you use a config without incremental saving). also together will always be loaded the part .32767

if I decide to make changes to the part, it must only have the kindness to reset at the end of the job the increase 32767, overwriting the previous one.

Is there any problem I can't see in this approach?

Clearly with windchill would be easier.

 

[320i S]

just a question, do you need the "read only" for libraries/archives?, or is it a much more general use?

 

[Hope]

just a question, do you need the "read only" for libraries/archives?, or is it a much more general use?

use in the absence of plm when I want to make a non-changeable part/axis or to make faster updating parts/axis. I create "high" the update of the read-only features.

In the specific case, I would like no one to overwrite the library and I think the most effective way is to change the writing permissions from windows.

 

[320i S]

without plm at wildfire times, I also read the storage folders and with an admin user, who could move and manage the files, so no one could overwrite or add new versions of the files in the archive folders (including books) and there were workbooks, where the files were moved by this admin user, to be able to work them later.
Obviously it is much more laborious so, but it worked.
But look at how it reacts I create if it cannot save in the target folders.