KLA#27
Guest
Hello everyone!! !
Can someone explain how the pack & go works? ?
thank you 1000!:finger:
Can someone explain how the pack & go works? ?
thank you 1000!:finger:
You're right the question is a generic "baby" but I've never used it and the online guide seems "fumosa".Oh, my God, that's a little generic. . .
we say that it is necessary to send to a third the data necessary to open/modify a project
What's your problem? What is not clear?
But isn't that you renamed some idw? and idw are in a folder under the same project or do you have a unique "project" for all your works?I have a problem with the pack & go: select the axieme, set the parameters, search now, in a few seconds find me all 3d, then I do again "try now" in connected files to find the tables, at this point there is a whole day! looking throughout the project file. I tried to select one folder at a time, but the time is cmq too.. .
Am I wrong? or is there a way to filter the files to search, such as the idw only connected, etc.? ?
Thank you all!
It's the same problem we have in the company and I don't tell you the anger I have for this... I have suggested several times that for each customer you should make a .ipj for each customer because if one needs the tables it is a mess with the pack & go.
This is the limit of the project:unique project!............ .
for that esistoni i pdm:finger::biggrin::mixed:Thanks tarkus, but how can you manage a project for machinery? having a database of details in common among all... We have encoded hundreds of sheets, pipes, turned and milled I don't tell you... then for each frame we go fishing around particulars already in production, then mount everything in the finished product with a lot of bolts whose designs (it-it) reside inside the project. to manage a project for each machine should I duplicate the standard production details, unified bolts, etc., within each project or not?? It would become so unmanageable.
No, it's not necessary to duplicate all the time:Thanks tarkus, but how can you manage a project for machinery? having a database of details in common among all... We have encoded hundreds of sheets, pipes, turned and milled I don't tell you... then for each frame we go fishing around particulars already in production, then mount everything in the finished product with a lot of bolts whose designs (it-it) reside inside the project. to manage a project for each machine should I duplicate the standard production details, unified bolts, etc., within each project or not?? It would become so unmanageable.:confused
our problem is that the pdm refers to only database project!!! is our limit and for this reason I ask how you do with different projects to inteff yourself to single database. The only thing that came to mind is to use the inventor vault but I have no experience about it.for that esistoni i pdm:finger::biggrin::mixed: