Jojo, once again, this error is already taken care of in more recent builds. Yes, I know what caused it but it's irrelevant <s>. You don't have to worry about working around this in the final release of the product.

Meanwhile...

We need to find out whether it is causing the report builder behavior that you see (I think it probably does) or whether you are seeing a separate bug.

I suspect that the two things are connected but I cannot prove it, because I cannot reproduce what you are seeing.

Can you run your code *without* the error handler? Do you get the same behavior, or different?

Can anybody else, reading this thread, reproduce what Jojo is seeing ?

>L<