on 6/1/00 8:15 AM, Chip Mefford at [EMAIL PROTECTED] wrote: > will get bumped in revision by one person working late at night > the others folks accessing the document via an alias will continue > on working on the old document, the work will fork off in > different directions, blah blah blah. Uh...hum... How is the different from not allowing alias' and having the users access the folder directly - it seems to me that this exact same problem can still happen, at least the way it was described. NOT using alias' won't miraculously make users smarter about working in a broken workflow environment. Harry
- Re: netatalk in production environments....(... Harry Zink/Netatalk List
- Re: netatalk in production environments.... wesley . craig
- Re: netatalk in production environme... andrew morgan
- Re: netatalk in production envir... wesley . craig
- Re: netatalk in production environme... Patrik Schindler
- [OT] [Re: netatalk in production... thomas.riewe
- Re: netatalk in production environments....(RFC) Steve Freitas
- Re: netatalk in production environments....(... Patrik Schindler
- Re: netatalk in production environments....(RFC) Luke McNeilage
- Re: netatalk in production environments....(... Chip Mefford
- Re: netatalk in production environments.... Harry Zink/Netatalk List
- Re: netatalk in production environments....(RFC) Tom Watson
- Re: netatalk in production environments....(... Patrik Schindler
- Re: netatalk in production environments....(RFC) Steve Freitas
