• This forum is the machine-generated translation of www.cad3d.it/forum1 - the Italian design community. Several terms are not translated correctly.

change the state of a project and block the modification of the parts

casadeimatty

Guest
Good evening to all, I write to ask you this question concerning inventor.
I would like to work with inventor 2010 and share my projects with other collaborators.
I would like to know if there is a possibility to make some files (which are parts or assemblies) blocked, i.e. not editable by an operator.
I do the example of the files that are in the libraries that are not editable and if not copying them in the work area.
I would like to avoid someone changing pieces after they have already been made.
a possible modification should be accompanied by a revision number, perhaps making a copy of the file.
I'm not using the vault.

thanks to anyone who wants to help me.
 
what you need is a document manager for modelers cad. the installed base vault has some features, perhaps it is not the best, but does what you require. if instead you think you can invest a little money, evaluate the version vault 360; I would recommend you productstream compass (other autodesk manager) but now do not install it anymore. I do not recommend other solutions of other sw, because usually the products of the same software house have good integration with distinct creation etc...
 
Thanks for the advice. I was also thinking about this solution. I work in a technical office where we are in three with a shared database. Until now we have not used the vault, but as you can imagine we have many copies of the same files. just to avoid having to assign different codes to practically equal pieces we would be willing to use the vault. the problem is I don't know if I can configure it alone. Can anyone give me a tip?
 
I don't remember if the base version of the vault also manages the possibility to block the changes or not, but for the rest would do what you need.

practically the only thing to set is a series of folders containing libraries, project files, where to copy open files etc identical on all computers that will use the vault. (when you open components with the vault, a copy is created locally, so all folder paths must be identical)

bringing old single-user projects into vault projects usually does not bring problems, the stakes arise if you want to transform a number of more projects into a single vault project because if you have to start redirecting libraries or eliminating multiple copies of the usual component, it usually touches one by one
 
solved without vault: to avoid assigning several codes to the same files I created a plug-in. from the project select a folder and when you find an identical file you resume the code.
 

Forum statistics

Threads
44,997
Messages
339,767
Members
4
Latest member
ibt

Members online

No members online now.
Back
Top