Thanks for confirming what I thought was happening.
This exemplifies what I was saying earlier about how AutoDesk doesn't
understand our needs. I can't just up & move that nut to the library file.
How would all the other assemblies that use it find it. Also, its part
number 550033 designates that it must be in the 550000-551000 folder.
Does anyone else design and draw a new product using generic file names in
an isolated folder and then, when the design is complete, assing part
numbers and move the files to the appropriate folders in an archive? Or it
is just me?
"DJSpaceMouse" wrote in message
news:2250DA97537776CAAEB8C6059B7612B5@in.WebX.maYIadrTaRb...
> Look within...
> > 1. When I open a file and check it out, in my Workspace, IV brings the
> > whole folder tree with the file which makes it inconvenient to have to
dig
> > down 4 layers to selcet the file that I want. Why does it do this and
can
> I
> > tell it to only bring the file and not the folders?
>
> I *think* that if you list all the subfolders in the Workgroup in your
> project file, this won't happen. I'm not sure on this one though. If you
> add all the subfolders to the project file, they'll appear red, but it's
> just a warning that it's a nested folder. It is crucially important that
> the subfolders appear BEFORE their parent.
>
> > 2. In order to fix the problems desribed in 1, I cut and paste the
files
> > into the workspace file and delete extra folders. IV doesn't like that
> much
> > especially with .idw files.
>
> Yes, because the referencing file is looking for the referenced file in
the
> subfolder that it was in, and you're moving it. Big no-no.
>
> > 3. If a file status is unresolved, I can put a place holder in one of
the
> > Workspace files, but not in their sub-directories. What a pain. I
could
> > list every directory and sub-directory as a workspace, but doesn't that
> > defeat the whole purpose of a filing systems?
>
> Again, adding the subfolder paths to the project will resolve this. But
> again, make sure the subfolders appear before their parent. Inventor will
> place the placeholder file in the wrong location otherwise. I call it a
> bug - Autodesk just says "don't do that then."
>
> > 4. I have a nut that is in a workgroup file, & that nut is used in a
> > chamber assembly that's in a library file. Whenever I open an assembly
> > containing the chamber, IV can't find the nut, so I locate it, and save
> the
> > assembly. Sure enough, the next time I open the assembly, IV still
can't
> > find that same nut.
>
> Inventor will not retain the change to the reference in the library
> assembly, because libraries are read-only. If you create a temporary
> project in which the library is listed in the Workgroup, then you can open
> the assembly, locate the nut, and the change to the reference will hold.
> But I don't think it's advisable for a library file to reference something
> outside of the library. I'd suggest moving that nut into the library so
you
> don't have problems later on.
>
>