Re: Report with trigger make me exhausted! Really need experienced people for my question.

It sounds to me like you have found a bug in the product. See if you can get support to replicate the bug and have them fix it.

Possible work arounds:
1) Do your create and drop in the calling form 2) Leave the table alone and just delete and insert into it

The broader question is to verify that you really need a temp table in the first place. I have written hundreds of reports and only needed a temp table
once or twice. Temp tables will have much worse performance than just running the report directly. Even if you are deciding what to query on the fly,
lexical parameters should be able to allow you to not use a temp table.

--
Paul Dorsey
Dulcian, Inc.
www.dulcian.com
212 595 7223
P.S.
If you would like to talk to Dulcian about a salaried position on our team,
please call me.
We have openings in NJ for developers, in CA for PERL developers.

tianh_at_my-deja.com wrote in message <7v9qm1$h$1_at_nnrp1.deja.com>...


>----I have a report with very clear design logic: In the BEFORE FORM


>Trigger, I create a temp_table, then in the AFTER FORM TRIGGER, I

>process the data and populate this temp_table, and in the After Report

>Trigger, I drop the table. (I use SRW package to create and drop this

>temp_table).

>

>BTW, you know, when I work on the layout, I manually create this

>temp-table in the Database, then after the layout is done, and complile

>the report(since the PL/sql use this temp_table), then I drop the

>temp_table manually. Then it works fine for the first time

>

>But after that I need to go to the SQL*Plus to drop this temp_table(the

>After Report Trigger does not fire for me).

>

>The next time when I open the report, and try to run it, ** the error is

>"report with uncompiled PL/SQL".

>

>Ok, then I manually create this temp_table again to gain successful

>compilation, and then drop the table manually, run the report, it is

>fine. (And of course I need to drop the table in sql*pus manually_.

>

>This errors happens every time I open the report. I need to repeat

>from **. But if I stay in the Report Buider, I can run it again and

>again without error(except dropping table manually).

>

>---Don't worry about my trigger not firing. When I incorporate this

>report into Form by creating a button to run this report, the trigger

>fires correctly, and I don't need to drop the table manually.

>

>    But another problem comes out. After I run this report several time

>starting in Form,  ***it just stop working. I checked the Report

>Backlog, the error is "REP-0002: Unable to retrieve a string from the

>Report Builder message file."--when I click the button for this report,

>it just does nothing.

>

>     Can you image how I make it work again? I open this file in report

>builder,then compile this file again, starting from that

>error"uncompiled PL/SQL", and redo the procedure described above. Then

>go back to the form to click the button and run the report, it works

>fine. However, after sereval time's running, I need to repeat from ***

>again!!!!

>

>    I know you may be tired of reading all the above stuff. But Please

>help if you know what is happening to me, what all these is for ?

>

>     I appreciate for any suggestion.

>

>Helen

>

>

>Sent via Deja.com http://www.deja.com/

>Before you buy.