by
cody84 » Wed May 02, 2012 5:50 pm
We had this problem, Varian told us every time you save over top of a method (when making changes/saved changes when processing) once the number of saves hits a certain number the file gets corrupted and must be made fresh. It has something to do with all the data gathered in the audit trail.
So, print out method, make a new one from scratch at certain intervals (every 6 months etc, depending on usage). He also suggested to create a NEW sequence for every run, don't open an old one and change it and save as new. Generally, this was the only way we used the software...open a previous method, sequence, summary report, everything and then save as new or save over top.
Another way to do it is create a new method for each one you have and save them as a template. Then each time you need a new one just use the template to save as a new method. Hope this helps