What is the best way to handle having multiple programmers at multiple stations working out of the same tool, matl, and operation directories?
Kevin
tool and matl libraries
Started by
bigprody
, Mar 21 2012 08:19 AM
5 replies to this topic
#1
Posted 21 March 2012 - 08:19 AM
#2
Posted 21 March 2012 - 09:59 AM
How do you mean? Using a server for the "shop's" libraries, or keeping it on individual workstations?
#3
Posted 21 March 2012 - 01:32 PM
Using a server, it seems that when we change our defaults to the server, MC allways finds its way back to the orignal directories.
#4
Posted 21 March 2012 - 02:26 PM
your defaults in the control defs have to be changed thru the machine defs or they will not stick. tool libraries & material libraries data paths have to be changed in the general machine parameters thru the machine defs. when saving use the file save icon ( top left ) first before pushing the green check button.
#5
Posted 16 April 2012 - 04:54 PM
I am currently using shared working directories for machine definitions and tool libraries, but I want to use my own default tool path settings. I can't figure out which setting actually changes this and lets me use my own settings, since the default ones we are using always have things to be changed everytime the default file a read only... :-/
So, can I keep the same machine definitions and everything as them, but pull my tool path defaults from my own file? And how?
So, can I keep the same machine definitions and everything as them, but pull my tool path defaults from my own file? And how?
#6
Posted 16 April 2012 - 05:38 PM
When moving files to a server I always remove the local versions.
Generally I zip them up in place and delete the files.
In this way, it can't run home.
Generally I zip them up in place and delete the files.
In this way, it can't run home.














