Garth Kidd wrote: >Further to my last mail; today's report run doesn't trigger the problem, so >I've got a new one. :) > > Not sure why this should change ; it still is a problem for us, with the test case you provided earlier in the thread. Has anyone else had this problem / got any ideas as to where we should look to solve it? Thanks David