Community
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"StefanTondl" <Hello,
href="mailto:stefan.tondl@advanced-logistic.de">stefan.tondl@advanced-logistic.de>
wrote in message
href="news:f12540c.-1@WebX.maYIadrTaRb">news:f12540c.-1@WebX.maYIadrTaRb...
The Adesk white paper suggests to use for multiple users working on the
same project a single ipj file for every user pointing to the local workspace,
with a included path file, refering to a ipj on the server containing all the
workgroup and library search pathes.
Why shouldn't I use a ipj located on
the server that points to the local workspace (every user will have the same
workspace directory like d:\work).
Thanks for any comments
Stefan
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"StefanTondl" <Hello,
href="mailto:stefan.tondl@advanced-logistic.de">stefan.tondl@advanced-logistic.de>
wrote in message
href="news:f12540c.-1@WebX.maYIadrTaRb">news:f12540c.-1@WebX.maYIadrTaRb...
The Adesk white paper suggests to use for multiple users working on the
same project a single ipj file for every user pointing to the local workspace,
with a included path file, refering to a ipj on the server containing all the
workgroup and library search pathes.
Why shouldn't I use a ipj located on
the server that points to the local workspace (every user will have the same
workspace directory like d:\work).
Thanks for any comments
Stefan
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"StefanTondl" <Hello,
href="mailto:stefan.tondl@advanced-logistic.de">stefan.tondl@advanced-logistic.de>
wrote in message
href="news:f12540c.-1@WebX.maYIadrTaRb">news:f12540c.-1@WebX.maYIadrTaRb...
The Adesk white paper suggests to use for multiple users working on the
same project a single ipj file for every user pointing to the local workspace,
with a included path file, refering to a ipj on the server containing all the
workgroup and library search pathes.
Why shouldn't I use a ipj located on
the server that points to the local workspace (every user will have the same
workspace directory like d:\work).
Thanks for any comments
Stefan
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Roger Farstad" <
href="mailto:roger.farstad@sensewave.com">roger.farstad@sensewave.com>
wrote in message
href="news:07BE8EBA320F4870361B3AA08E19E90D@in.WebX.maYIadrTaRb">news:07BE8EBA320F4870361B3AA08E1......
Another drawback, could be that if you temporary
want to switch to another project, you will have to check in all parts from
the first project before you check out parts from the second project to avoid
conflict for different part with equal names.
For instance if you in both projects have a part
called "shaft" and this is not the same part, then you could get problems if
the part is not checked in before the other "shaft" is checked out. In minor
project I use to check out/in all the parts, so for me it is small
problem.
Roger
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"StefanTondl" <Hello,
href="mailto:stefan.tondl@advanced-logistic.de">stefan.tondl@advanced-logistic.de>
wrote in message
href="news:f12540c.-1@WebX.maYIadrTaRb">news:f12540c.-1@WebX.maYIadrTaRb...
The Adesk white paper suggests to use for multiple users working on the
same project a single ipj file for every user pointing to the local
workspace, with a included path file, refering to a ipj on the server
containing all the workgroup and library search pathes.
Why shouldn't I
use a ipj located on the server that points to the local workspace (every
user will have the same workspace directory like d:\work).
Thanks for any comments
Stefan
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"KJohnson" <kj@sensoft> wrote in
message
href="news:78EE35C9CE125DE2ED3B6CFD50EC68C8@in.WebX.maYIadrTaRb">news:78EE35C9CE125DE2ED3B6CFD50E......
Why don't you check out to two different working
folders? Local workspace.
Kathy Johnson
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Roger Farstad" <
href="mailto:roger.farstad@sensewave.com">roger.farstad@sensewave.com>
wrote in message
href="news:07BE8EBA320F4870361B3AA08E19E90D@in.WebX.maYIadrTaRb">news:07BE8EBA320F4870361B3AA08......
Another drawback, could be that if you
temporary want to switch to another project, you will have to check in all
parts from the first project before you check out parts from the second
project to avoid conflict for different part with equal names.
For instance if you in both projects have a
part called "shaft" and this is not the same part, then you could get
problems if the part is not checked in before the other "shaft" is checked
out. In minor project I use to check out/in all the parts, so for me it
is small problem.
Roger
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"StefanTondl" <Hello,
href="mailto:stefan.tondl@advanced-logistic.de">stefan.tondl@advanced-logistic.de>
wrote in message
href="news:f12540c.-1@WebX.maYIadrTaRb">news:f12540c.-1@WebX.maYIadrTaRb...
The Adesk white paper suggests to use for multiple users working on
the same project a single ipj file for every user pointing to the local
workspace, with a included path file, refering to a ipj on the server
containing all the workgroup and library search pathes.
Why shouldn't
I use a ipj located on the server that points to the local workspace
(every user will have the same workspace directory like d:\work).
Thanks for any comments
Stefan
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Roger Farstad" <
href="mailto:roger.farstad@stoltoffshore.no">roger.farstad@stoltoffshore.no>
wrote in message
href="news:769F2955D8C94E0529823C2066A5889A@in.WebX.maYIadrTaRb">news:769F2955D8C94E0529823C2066A......
I belive this is not possible with just one
project file. You are not allowed to define more than one workspace folder in
each ipj-file.
Roger
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"KJohnson" <kj@sensoft> wrote in
message
href="news:78EE35C9CE125DE2ED3B6CFD50EC68C8@in.WebX.maYIadrTaRb">news:78EE35C9CE125DE2ED3B6CFD5......
Why don't you check out to two different
working folders? Local workspace.
Kathy Johnson
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Roger Farstad" <
href="mailto:roger.farstad@sensewave.com">roger.farstad@sensewave.com>
wrote in message
href="news:07BE8EBA320F4870361B3AA08E19E90D@in.WebX.maYIadrTaRb">news:07BE8EBA320F4870361B3AA......
Another drawback, could be that if you
temporary want to switch to another project, you will have to check in all
parts from the first project before you check out parts from the second
project to avoid conflict for different part with equal
names.
For instance if you in both projects have a
part called "shaft" and this is not the same part, then you could get
problems if the part is not checked in before the other "shaft" is checked
out. In minor project I use to check out/in all the parts, so for me it
is small problem.
Roger
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"StefanTondl" <Hello,
href="mailto:stefan.tondl@advanced-logistic.de">stefan.tondl@advanced-logistic.de>
wrote in message
href="news:f12540c.-1@WebX.maYIadrTaRb">news:f12540c.-1@WebX.maYIadrTaRb...
The Adesk white paper suggests to use for multiple users working on
the same project a single ipj file for every user pointing to the local
workspace, with a included path file, refering to a ipj on the server
containing all the workgroup and library search pathes.
Why
shouldn't I use a ipj located on the server that points to the local
workspace (every user will have the same workspace directory like
d:\work).
Thanks for any comments
Stefan