Autodesk Inventor

[#1]

If I have a part or assy file open, can I change what project [file] that the part or assembly belongs to?

[#2]

pack n go into another project folder would be one if not the only way?!?!

Not aware of any option to switch projects on parts & assy's after they've been modeled in another project.

[#3]

acknowledged

thanks

[#4]

Can't you just copy the files into another project? 

From what I can tell, it seems that Inventor isn't tracking what project file the .IPT or .IAM is associated with, so much as it's tracking where that .IPT or .IAM is located, and what project file that location is associated with.

When I get error messages about the file I'm trying to open not being part of the active project, it's because I'm opening something from a location outside of my currently active project.  I just move the file and things are fine again.

[#5]

You could manually copy the files sure, but due to file links and just in case there's Content Center parts that I did not save into the Project folder (and have forgotten or unsure if there are any CC parts in there), I've always used Pack N Go to ensure the links stay put.

[#6]

Or you could do what we do and just make one project file that encompasses all file locations.

[#7]

Unfortunately, we have different departments that operate free willy.  An no one with authority cares to take on actual cad management for the entire location.

If I had authority I would but half the users would ignore the protocols anyway when managment doesn't reinforce the rules.

So if I read the information above right, if someone creates a part / assy on their drive and I copy it over, it will open under my all encompasing project?

If I instruct them to copy and create assy's on my [network] drive, it will still open under my project?

If that is the case, it should be a non-issue.

[#8]

---

divingdoug wrote:

Unfortunately, we have different departments that operate free willy.  An no one with authority cares to take on actual cad management for the entire location.

If I had authority I would but half the users would ignore the protocols anyway when managment doesn't reinforce the rules.

So if I read the information above right, if someone creates a part / assy on their drive and I copy it over, it will open under my all encompasing project?

If I instruct them to copy and create assy's on my [network] drive, it will still open under my project?

If that is the case, it should be a non-issue.

---

So long as all the files are located in a directory that's included in your project, then there's no problem. 

Well, maybe - if the directory is included as a library, then anything in it will be read-only.  I've got one main project file that I've set up, which addresses my workspace, and I've got libraries that are accessed by that project.  I've got a separate project that I use when I want to edit my hardware library.

But, yeah, if everyone copies their stuff onto a network location and you copy the files from there to your workspace, then so long as you got all the components you'll be good to go.  If stuff is from content center, you just have to make sure that everyone is working off the same content center libraries, and you should regenerate all the parts from there pretty transparently.

[#9]

to avoid the worry or concern as to whether or not you got all the files, this is where Pack N Go and including the "Copy to Single Path" option comes in handy 

[#10]

Thing about Pack-n-Go, it works best when you've already got the project file.  If you're using it outside of your project, it gets a little squirrely.  For instance, I've got an external drive that's got about 10 years worth of Inventor / MDT / ACAD files on it, in about 15,000 directories.  Pack-n-Go is pretty much worthless there, because it doesn't recognize the directory structure.