Doubt - Choose from 2 Query in the same report.

[Jeremias]

Good afternoon to all,

I have 2 different queys .... and the idea would be to create 1 report which the user would call (choose) one of them to generate the report.

Does anyone know the routine or have any idea how I do it ??

abs,

[victorhugomuniz]

maybe right a gambiarra as follows ..
you put two subreport inside one and then printa one or another according to a certain parameter ..

now a basic question ..
Why can not you do 2 rel and decide which call in your front end routine?

[Jeremias]

VICTOR,

I gave this idea to my supervisor here, to create two reports .... but he is one of those people who think best to complicate than to facilitate .... rss, will understand: roll :.

I'm breaking my head here ...

[victorhugomuniz]

Can not you pass the dataset for your report instead of having the query inside it?

Then you would decide for the query that will use, perform and send the data fetch

[victorhugomuniz]

take a look [url=http://download.oracle.com/docs/html/A7 ... tm#1009556]aqui

[Jeremias]

Thanks for the attention, I'll try to do it that way, I'vê already gotten an idea.

I even apologize for the newbie question ... rss

[Diego_Mello]

Oops ...
What I'm going to say will not help your doubt at all, but it's my opinion. : P
It is much better to work with multiple layouts in the same report.

imagine that you have 5 reports that do almost the same thing:
1) The report A is synthetic;
2) B is analytical;
3) The C break by group;
4) The d breaks;
5) o and is retroactive;

there ask you to ... I do not know ... increase the decimal places of a field.
thinks of the work that you will have picking up the Reports, opening one at a time, checking case by case.

I, at least, prefer you in the same place.
is almost the concept of package! hahahahaha

[ricards]

Friend, create your reports based on Record Group

You create the entire rule of your Reports in a package or procedure in the database with all queries.

Your report is much faster and you can better organize the data for large reports.

follows the tutorial that I made of report based on Record Group, is very easy to use this way to build reports.
http://en.glufke.net/oracle/viewtopic.php?t=6653

Hugs

[Rafael Martelli]

You can use an unnion on your query!
there in the WHERE clause of your selects you place the parameter that will identify which Select will run.
In the case of 2 select (A and B), you create a parameter that will receive which report will be executed (A or B), there in the WHERE of each SELECT you put the condition:

0]]

The problem is that you will always run the 2 SELECTS, and this will take.
Now if the difference between your select is the WHERE clause, just create a parameter (p_where) that receives the WHERE statement in the Trigger After Parameter Form, and in the Select to put a & p_where.

[Rafael Martelli]

Another way to do, if your select is well complex, or the execution conditions are many, is to create a package that makes Select dynamically and insert the result in a temporary. In the report, in the main query, do the Select in the temporary.