This behaviour is current.
Same thing happens if I add the Ipart library search path and its proxy path
to my Default project.
Same thing happens if I create a new assembly (with newly spawn childrens,
derived directly from the Iparts) in one of the existing projects.
Same thing happens if I create a new project, add the library (& proxy)
paths & create a new assembly.
My Iparts were created in a different location, so I thought I'd better move
it to the libraries (using Windows Explorer cut & paste) before starting to
use it in assemblies, when I came across this "curiosity".
I am fairly new to Iparts, so I guess I must have done something wrong
somewhere...
Regards,
Danny
"Sean Dotson" wrote in message
news:3252E58D00147640B185CDB5EC5F80BF@in.WebX.maYIadrTaRb...
> OK that looks good. I'm at a loss why some would be created in the proxy
> location and others not. Check the dates on the children *not* in the
proxy
> location. Maybe they were created in the past before you set up the proxy
> path?
>
> --
> Sean Dotson, PE
> http://www.sdotson.com
> Check the Inventor FAQ for most common questions
> http://www.sdotson.com/faq.html
> Watch out Philly, Tampa's on a roll...
> -----------------------------------------
>
>