The inner workings of I Parts?

[Anonymous]

I have R 5.3 loaded on one drive and R6 SP1 loaded on the same HD but on a
separate partition. I have the project files located on a separate HD that I
work on with 5.3 and I have made duplicate of that file on a separate
drive which I will work on with R6 SP1. The projects in 5.3 and 6 have been
set to their perspective separate folders.

The question is why even though all my IParts have been copied over to the
duplicate folder on the other drive (where I do all my R6 work) does it
migrate the ones I use in R5.3?..I mean they are not even connected or are
they?

Albert

[Anonymous]

probably b/c the iParts were part of library paths and their locations are
hard coded into the assembly so that they can ignore the project paths upon
opening and supposedly save opening time.

--
K


"Albert Allen" wrote in message
news:4E31814A9737A1D215FECE126B37C8E3@in.WebX.maYIadrTaRb...
> I have R 5.3 loaded on one drive and R6 SP1 loaded on the same HD but on a
> separate partition. I have the project files located on a separate HD that
I
> work on with 5.3 and I have made duplicate of that file on a separate
> drive which I will work on with R6 SP1. The projects in 5.3 and 6 have
been
> set to their perspective separate folders.
>
> The question is why even though all my IParts have been copied over to
the
> duplicate folder on the other drive (where I do all my R6 work) does it
> migrate the ones I use in R5.3?..I mean they are not even connected or are
> they?
>
> Albert
>
>