I'm embarrassed to say that there has been a bug in the "break" command (for loops) since it was introduced, probably. Up till now, the effect of "break" has been to invalidate the loop continuation condition. The loop would not proceed to the next iteration -- but it would, however, continue to the end of the current iteration. The new behavior, which I'm sure is what users would expect, is that the thread of execution of the current loop breaks immediately after the "break" command. Simple test case: <script> loop 100 print "One" break print "Two" endloop </script> Up till now you'd see "One" and "Two" printed once; now you see just "One". I hope this hasn't caused anyone grief in writing complex scripts. Allin