part files and active project

[GiGa]

a curiosity: creating a new part with a given active project, the "record" part somehow the project with which it was created? or is she completely "swisted"?
can you extract information about the project with which it was created?

ps: I ask for mere reasons of confidentiality. . It happened that I was asked to "flight" a small part, but having opened several files of another project (of another client), I did not want to close them. . .

 

[Avoplus]

in the file should only be recorded the path of the project file (it is true that, if you open a file outside the project environment, inventor alerts with a message). However, as far as I know, you cannot trace back to the information contained within the project file from the cad...

 

[GiGa]

in the file should only be recorded the path of the project file (it is true that, if you open a file outside the project environment, inventor alerts with a message). ...

ok, but more than "read" within the file the path (and therefore of the file project), I simply think see that the file is on a path other than that of the active project, with relative notice. . .
It wasn't like that, it wouldn't be (for me, in terms of confidentiality) a good thing...

 

[Ilario]

you are as you say giga, in the file nothing is stored if not handwritten within iproperties. in fact is the project that signals the opening of a file outside of it, not the file.

 

[KLA#27]

As the matter has arisen, I take advantage of it to ask for lumens. .

first I apologize to those who opened the discussion if "I do it my", but I try to follow the rule of the forum not to create doubles...:biggrin::tongue::biggrin:

what is the best way to manage project files and what is their precise purpose? ?

I currently work with a single "company" project where all files are placed (on advice of my installer-reseller)

But wouldn't it be better to create a project for every contract? ?

Thank you! !

 

[Ilario]

depends, the usefulness of the project file is to have the organization of objects related to ogi project made, subfolders, libraries, templates and anything else, neatly divided.

I also use only one project file for everything, my need is derived from the fact that I often use objects, perticolars, bookcases, and templates in common with all the different machine projects (e.g. the axieme project has inside it an object b that is also used in the project c) if so I should not be able to double each time I create a set with shared pieces here and there.

I would say that the subdivided projects are comfortable for offices with multiple different customers and therefore have templates, standards, perticolars etc... different according to the customer himself, while the unique project is useful (to those who do not use vault) in a manufacturer that "draws" only for itself and with a varied production.

 

[diegus]

....but wouldn't it be better to create a project for each contract? ?

Yes, it is.
the problem is that then it becomes annoying, for some, the fact that you can not insert objects already used in another project in the active project (remaining that with few settings it is still possible). then, most of the time, the advice of those who do not want to have rogne is: "use one project"!

explain to you what the project file needs now would be long and complicated.

 

[Ilario]

Yes, it is.
the problem is that then it becomes annoying, for some, the fact that you can not insert objects already used in another project in the active project (remaining that with few settings it is still possible). then, most of the time, the advice of those who do not want to have rogne is: "use one project"!

explain to you what the project file needs now would be long and complicated.

what might interest me, what would be the few settings to use objects from different projects?

 

[diegus]

in the project you can set two things:
1) the library folders that are folders where you will go to put objects that can be used by different projects but which are and must remain equal in all projects (think as if they were objects of the content center ie standarderia); for security reasons this folder is automatically protected in writing (the object present in various projects cannot be adapted in the measurements in the current project).

2) "work group search paths" in this string you can indicate folders belonging to other projects where you can go to pick up components. This is a little more risky because the component of the project to which it is inserted in a set of the project b, if it is modified, will keep the change in both projects.

 

[davide75]

and do the pack & go doesn't become annoying if you have a unique project for all jobs? ? ?

 

[Avoplus]

you are as you say giga, in the file nothing is stored if not handwritten within iproperties. in fact is the project that signals the opening of a file outside of it, not the file.

Bah... As far as I could see on my skin, when you create a project, you create a real "environment" within which, inventor manages the cad files and libraries (in other words, you give it a reference directory). as said giga, in practice, within the cad file is stored the position (including full name) of the project file with which it was created. at the opening of the file, it is inventor who compares the paths and, if the file is not located within the project environment (=in a folder/sub-fold of the project "main"), warns the user. :smile:

 

[Ilario]

and do the pack & go doesn't become annoying if you have a unique project for all jobs? ? ?

Of course, but for what I use it, it is negligible

 

[Ilario]

Bah... As far as I could see on my skin, when you create a project, you create a real "environment" within which, inventor manages the cad files and libraries (in other words, you give it a reference directory). as said giga, in practice, within the cad file is stored the position (including full name) of the project file with which it was created. at the opening of the file, it is inventor who compares the paths and, if the file is not located within the project environment (=in a folder/sub-fold of the project "main"), warns the user. :smile:

I don't know if we're telling us the same thing differently, but from what you say, it seems that the path of the project file is stored within the file, but it's not.
do a test, create a file with a different active project, save it within the workgruop of that project, now close and change project, browse for folders and copy the file created first within the new workgroup... you will see that the file opens it anyway even if it was created for a different project.

the question is that it is the project file that has the paths, if you open files outside its paths then it alerts you, but the files, inside them, have not stored anything.

 

[Ilario]

in the project you can set two things:
1) the library folders that are folders where you will go to put objects that can be used by different projects but which are and must remain equal in all projects (think as if they were objects of the content center ie standarderia); for security reasons this folder is automatically protected in writing (the object present in various projects cannot be adapted in the measurements in the current project).

2) "work group search paths" in this string you can indicate folders belonging to other projects where you can go to pick up components. This is a little more risky because the component of the project to which it is inserted in a set of the project b, if it is modified, will keep the change in both projects.

I have given an eye and indeed these things I have never evaluated them, I have to experience if the thing can create problems, in the sense that here where I work to create "projects" is on the agenda, so currently, as long as I create subfolders and save my files in there and I'm fine, while with this new method, whenever I create a new project I should map time for all the folders I need etc... But not the discard as a possibility, it could be a more neat and comfortable system.... thanks

 

[Avoplus]

I don't know if we're telling us the same thing differently, but from what you say, it seems that the path of the project file is stored within the file, but it's not.
do a test, create a file with a different active project, save it within the workgruop of that project, now close and change project, browse for folders and copy the file created first within the new workgroup... you will see that the file opens it anyway even if it was created for a different project.

the question is that it is the project file that has the paths, if you open files outside its paths then it alerts you, but the files, inside them, have not stored anything.

I remembered I had recovered the complete path of the project file by means of a macro but, evidently, it went fishing in the "configuration" of inventor and not in the single file. My mistake, I guess. :redface:

Hi.
:smile: