drew wrote:
On Thu, 2011-04-07 at 09:43 -0400, Dan Lewis wrote:
Dan Lewis wrote:
The Base Guide outline for chapter 4 contains this subheading
under Report Wizard:
Tables, Queries, Views, and SQL.
I understand how to create a report from a tables, queries, and
views. But creating a report using the wizard from SQL is something
that I do not understand. How is this SQL statement created?
The SQL statement is created using the Query Designer, in this context
most likely in SQl View mode.
Page 1 of
the Report Wizard has the Tables and Queries dropdown list. How does
this SQL statement become visible in the list?
Jean: Chapter 4 of the Base Guide is completed with the exception
of the Report Wizard section. I should be able to finish this section
in about a week with the SQL part mentioned above. Without more
information about how a SQL statement can be accessed by the Report
Wizard, I will limit the section on creating a report from to the
following: tables, queries, and views.
Dan
As a follow-up on SQL: Is the SQL referred to in the outline the
SQL command entered into the Oracle Report Builder?
Hi Dan,
The Query designer can be called directly from the Report Builder
interface, the generated SQL statement is then fed back into the Report
definition.
After doing some
research, the Report Builder can create a report based upon a SQL
command. I don't see how the Report Wizard can.
Again, for the older wizard the SQL is generated prior to the running
the wizard and you connect to this, as you would a Table. Additionally,
it would be common to use the Query designer to generate a complex SQL
statement and then to turn this into a VIEW, the wizard then connects to
the VIEW, as if it where a TABLE.
//drew
Little confusion on my part here. A VIEW is a virtual table or a
stored query according to the hsqldb user's guide. I also notice that
the View Design dialog has a Design View and a SQL View. This is similar
to the Query Design dialog that also has these.
When I save something using the Query Design dialog, it is saved
as a QUERY. When I save something using the View Design dialog, it is
saved as a VIEW. So, as I understand it, I would write the complex SQL
statement (that I wanted to use) in the View Design dialog and save it.
Then I would access it as a VIEW in the report wizard. The SQL statement
would have the form:
CREATE VIEW <viewname>[(<viewcolumn>,..) AS SELECT ... FROM ... [WHERE
Expression]
[ORDER BY orderExpression [, ...]]
[LIMIT <limit> [OFFSET <offset>]];
This seems like I would be just creating a VIEW, using SQL, that
would be only needed for the report. In the Report section of the Base
Tutorial, a query was created for the patient phone number report. Is
this an example of what you are saying?
If this is not what you are saying, I would like to have an
example of a complex SQL statement if possible.
Dan
Jean: If the SQL mentioned in the Report Wizard section belongs to
a section on the Report Builder, then perhaps the SQL should be removed
from the Report Wizard section? Also perhaps a note at the end of the
Report Wizard is needed. There mention that the Report Builder is
available and that SQL can be used as a source for a report.
Dan
--
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help
