We have a script that has basically stopped working. When you attempt to run it, it doesn't error or anything it just does nothing! I've tried starting it in debug mode (F11) and it goes like it's going to start and then it's done. It's as if the test is blank. The weird thing, I can copy and paste the script to a new test and save it and (after reattching all the libraries and such) it works fine again. This has happened 2 times now, the first time being about a month or so ago. Has anybody else had this problem? And is there a better solution than copying the test into (yet) another new test? [img]/images/graemlins/confused.gif[/img]
Also, I've tried using the "Save As" and save it local to another networked drive, doesn't matter they still fail. It's only when I copy paste the script to a new test.
A good rule of thumb is to never measure with your thumb.
Steve I have seen this before in v9.2 we had around 100 installs but it only happened on 2 machines. After extensive investigation I could find no differences between those 2 machines and those that didn't display the behaviour.
Used the same workaround, copied contents of script.mts file and saved it again.