ReportBuilder Exception Handling

rbuser

I encounter a problem that at first glance is not a big issue, but can be
rather unhelpful when the product is delivered.Whenever an exception in RB
occurs, it always filters down to "Cannot generate report.". I looked at the
source code, but it should actually add the error message at the end, but
the exception text in the handler (e.Message) is always empty.

Did anyone else encounter this? And if yes, how can it be fixed?

-------------------------------------------------------------------
Marco Heine
QUMAS
Enterprise Compliance Management
Visit our Website: www.qumas.com

digitalmetaphors

Most often a poorly coded RAP event handler which compiles in RAP, causes an
exception when the report generates or there is some problem in the printing
process. The message is not displayed for the exception and this is
intended.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

I see... Is there anything planned for RAP in the future that gives a bit
more of a conclusive error-message? The usual try/except in RAP would be a
very usuful feature (especially since commands in RAP can raise them .

Cheers...
-------------------------------------------------------------------
Marco Heine
QUMAS
Enterprise Compliance Management
Visit our Website: www.qumas.com

digitalmetaphors

We haven't added this optimization yet. Agreed, it would be cool to know
which RAP event handler is causing the problem and the actual cause of the
exception.


Cheers,

Jim Bennett
Digital Metaphors