Community
Inventor Forum
Welcome to Autodesk’s Inventor Forums. Share your knowledge, ask questions, and explore popular Inventor topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Project files for multiple users, semi isolated mode

7 REPLIES 7
Reply
Message 1 of 8
StefanTondl
415 Views, 7 Replies

Project files for multiple users, semi isolated mode

Hello,
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
7 REPLIES 7
Message 2 of 8
Anonymous
in reply to: StefanTondl

We use just one ipj -file with workspace set to
c:\work which is identical for alll of our users, and multiuser set to
Semi-isolated. I think this works fine, but I don't know if there are any
"hidden" drawback by this.

 

Roger


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Hello,

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

Message 3 of 8
Anonymous
in reply to: StefanTondl

Roger is correct.  That will work just
fine.  The only drawback I can think of is that with every user having
his/her own Personal Project File, he/she can specify a different number of Old
Versions to save.  Big deal, huh?


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Hello,

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

Message 4 of 8
StefanTondl
in reply to: StefanTondl

thanks for the info...

Stefan
Message 5 of 8
Anonymous
in reply to: StefanTondl

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">
Hello,

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

Message 6 of 8
Anonymous
in reply to: StefanTondl

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">

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">
Hello,

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

Message 7 of 8
Anonymous
in reply to: StefanTondl

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">

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">

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">
Hello,

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

Message 8 of 8
Anonymous
in reply to: StefanTondl

If you have two different projects why don't you
have two IPJ files.  If you have one default IPJ file for two different
projects with parts with the same name you could get into trouble.  The IPN
and IDW may get confused about which part they want.

 

Kathy Johnson


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

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">

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">

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">
Hello,

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

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report