Hi, > These particular tests are setup up with a try/catch block to trap a > different error but end up trapping this one instead.
Sure but why does the stand alone code which replicates the test (posed in this thread) get the correct exception? Sort of implies there some sort of state going on but looking at the test I can't see where as it creates a new array and new sort every time. Justin
