Bug? RB - 6.02 Enterprise

rbuser

I have 3 reporting components on a form which is used in an enduser solution
within our new application. They are respectively used for 3 reporting areas
in the app: Designing reports which are stored in a database; Runtime
previewing in everyday use (print this invoice etc); and Exporting data once
a preview report has been run. I have used 3 Tppreport components to
simplify managing all the different stuff I have had to code for the 3 areas
of functionality. This has been working well until I wrote some new reports
recently. With these reports only, if they have been opened once with one of
the report components, then if I try and load with another component I get
gthe following error message:

"Unable to load BeforePrint code for GroupFooterBand2:no object with this
name exists"

followed by some nasty AV which prove pretty fatal.

So if I preview such a report then click on my export button I get the
error; or if I preview then decide to open the report with the Designer I
get it. I have trying calling every "reset" method or every object I can
think of to no avail. The only solution is to either destroy my hidden but
persistent end user form, or to merge the functionality into a single
component. As it happens we are releasing the product today (time is of the
essence) so I've just collapsed Previewing and Exporting into one TppReport.
I really need to keep Designing separate, so I destroy and re-create the
form for this bit.

Clearly something is not being released from memory, but what...and why only
with this set of reports. They are more complex than other reports, but I
think the only real difference is that they have 3 groups in them.

Any ideas.....this almost gave me a heart attack since we were just about to
ship when we spotted the problem.

Paul

digitalmetaphors

One way you can get this message, is if the username of the groupfooterband
is changed. This probalby occurs from the fact that a component with this
name already exists on the form. If the template is loaded onto a form, and
a ppGroupFooterBand1 already exists in another report on the form, then the
naming conflicts have to be resolved. When this happens, the names of the
objects being loaded are changed, and for some reason which we can't
reproduce, the RAP event handler can't be assigned. What you can do, is
unload the template (load a blank template) from the last report which was
used, when you take an action to load a template into one of your other
reports. This should eliminate the chances that naming conflicts will have
to be resolved with multiple report components on the same form.


Cheers,

Jim Bennett
Digital Metaphors