2004-10-12 05:23 PM
2004-10-12 05:45 PM
2004-10-13 02:35 PM
Matthew wrote:
Yes, each person should save their own PLC to their local machine. This makes it possible to save changes without committing to a send and receive, and provides a bit of security in case of a network or server failure.
2004-10-13 02:46 PM
Just to emphasize this... be aware that AutoSave does not work over a network. If you don't have a local copy, there is no AutoSave should you experience a crash.Umm... yeah it does. We have 10 people autosaving over a network all day, both with and without saved PLC files.
2004-10-13 03:16 PM
TomWaltz wrote:Trust me... don't count on it!Just to emphasize this... be aware that AutoSave does not work over a network. If you don't have a local copy, there is no AutoSave should you experience a crash.Umm... yeah it does. We have 10 people autosaving over a network all day, both with and without saved PLC files.
2004-10-13 05:06 PM
Trust me... don't count on it!I don't know what to tell you, but it's worked nearly flawlessly for a year, with projects ranging from 2 to 10 people.
2004-10-13 06:04 PM
2004-10-13 10:43 PM
2004-10-13 11:57 PM
Matthew wrote:
You have an exceptionally robust network with a top notch IT guy. That probably has something to do with your experience. Not everyone is so fortunate. I don't think others should assume they will have the same results you do.
Matthew wrote:
I am sure Woody has seen the problems first hand. Thus the warning. I agree with him that for the average user saving the PLC locally is the safest route.
2004-10-14 12:02 AM
The program appears to be Autosaving but it is not. When working on a Teamwork project, the file in the Temporary folder is the .plp (which does not save anything without a Send and Receive).Just to clarify; the above should read: