It's been rumoured that Robert Graham Merkel said: > This is a known problem with the transaction report - it barfs on > large reports. Unfortunately, > there is no easy fix, beyond rewriting the transaction report totally > (which is happening for 2.0). out of curiosity, what, exactly, is the problem? Some O(n^2) loop? Does it come back eventually? --linas