An iPart child question...

[dan_mayers]

We had a server meltdown and have had to rename the main server for our iParts. I am now finding that many of the children (not all) are still trying to look to the old server for the iPart factory. From the Sean's tutorial, I had understood that the project file should be telling the children where to look for the parent file, and had set up our project files to support this.

Am I pulling a stupid, or is this not the way it is supposed to work?

Is there a way to get the children to update other than opening each individual file and resolving them?

Thanks for your help!

Dan

[Anonymous]

Did you have the server mapped to a drive letter? If not that's your
problem. Projects look for a drive letter, and all kinds of problems can
result from using unmapped drives.

If this does not fix it, then try this alternative:
Try using an include file in your project that lists the libraries on
the new server drive. Place this ipj in the root of your library
directory. and remove the libraries from your existing project.

Dennis

dan_mayers wrote:

> We had a server meltdown and have had to rename the main server for
> our iParts. I am now finding that many of the children (not all) are
> still trying to look to the old server for the iPart factory. From the
> Sean's tutorial, I had understood that the project file should be
> telling the children where to look for the parent file, and had set up
> our project files to support this.
>
> Am I pulling a stupid, or is this not the way it is supposed to work?
>
> Is there a way to get the children to update other than opening each
> individual file and resolving them?
>
> Thanks for your help!
>
> Dan
>

--
Dennis Jeffrey
Autodesk Product Consulting and Training
Center for Design Excellence
http://www.design-excellence.com
260-459-1311 ext 221 or 800-550-6070 ext 221

[Anonymous]

Dan,

Did you use UNC naming in the Project File?

I know Hal is a proponent of this format (and it's good/fast as long as
the server doesn't blow up and need to be renamed), but if the IPJ is
set to a relative file structure, it would seem to me that there should
be no resolution problems.

Anyhow, try the migration assistant and see if it will walk through the
children folders and update the children to their "new" parents. (set up
a new IPJ to do this)

QBZ


"dan_mayers" wrote in message
news:f187561.-1@WebX.maYIadrTaRb...
> We had a server meltdown and have had to rename the main server for
our iParts. I am now finding that many of the children (not all) are
still trying to look to the old server for the iPart factory. From the
Sean's tutorial, I had understood that the project file should be
telling the children where to look for the parent file, and had set up
our project files to support this.
> Am I pulling a stupid, or is this not the way it is supposed to work?
>
> Is there a way to get the children to update other than opening each
individual file and resolving them?
>
> Thanks for your help!
>
> Dan
>

[dan_mayers]

Thanks for the quick replies. All of the files are linked to the project through an included project file that references the directories using UNC. It should have been a simple matter of changing the included file reference, but that did not work.

I'll try the migration assistance route and see what happens. ...

Thinking about this now, I wonder if it has something to do with multiple levels of project files. If migration assistance doesn't work, I will try some experiments with project files. (Hopefully I won't blow something up. 🙂 )

Dan

[Anonymous]

Even without server meltdown (just changing servers) I have run into
this on a few iParts. I have attributed it to stupid iPart children. I
have experienced some of the children finding their parent and some of
them not (same parent, different projects, project files OK). For the
stupid ones, I just show them where their parent is and hope they don't
breed.

dan_mayers wrote:

> Thanks for the quick replies. All of the files are linked to the project
> through an included project file that references the directories using
> UNC. It should have been a simple matter of changing the included file
> reference, but that did not work.
>
> I'll try the migration assistance route and see what happens. ...
>
> Thinking about this now, I wonder if it has something to do with
> multiple levels of project files. If migration assistance doesn't work,
> I will try some experiments with project files. (Hopefully I won't blow
> something up. 🙂 )
>
> Dan
>

--
Hal Gwin
Mechanical Designer
Xenogen

W2K SP4
Dell Precision 650
Dual 2.66 GHz Xeon
1.5 GB DDR
Quadro4 900 XGL
nVidia 6.14.10.4403 w/registry update
Dell UltraSharp 19" LCD