Oracle Reports Builder

Oracle 9i Reports uses JSP (JavaServer Pages) technology to embed reports directly into web pages, enabling dynamic report generation within web applications. ASP is Microsoft's technology, CSS is for styling, and HTML is the markup language itself. JSP allows seamless integration of Oracle reports with Java-based web infrastructure.

Tabular Report is the most fundamental report type, displaying data in simple rows and columns format similar to a database table. Form reports present one record per page, Matrix reports show two-dimensional data with row and column headers, while Single Query refers to a data source approach, not a report type. Tabular reports form the foundation for more complex formats.

Groups organize report columns into logical sections, enabling hierarchical display and summary calculations at different levels. Fields are individual data display units, Links connect related data, and Summaries perform calculations. Groups provide the structural organization that determines how columns relate and repeat in the report.

A Group Left report is a specific layout style where the master (grouping) column is placed to the left of the detail columns. This prevents the master value from repeating for every row of detail data, creating a clean, hierarchical view of the information.

The Report Editor is the primary environment in Oracle Reports where developers can manipulate objects. It contains several views, including the Layout Editor (for visual design) and the Data Model Editor. While the Layout Editor is where direct manipulation happens, 'Report Editor' is the parent container for these tools.

The Data model defines what data gets retrieved by specifying queries, data sources, and column definitions. It acts as the blueprint for data access, determining which tables are queried, how they're joined, and what columns are available. Data Query, Data Wizard, and Data Fields are components or tools, not the comprehensive model itself.

The Report Editor's Paper Layout View is specifically designed for formatting paper-based reports, allowing precise positioning and sizing of objects on the page. Object Navigator is for object management, Data Model Editor handles queries, making Paper Layout View the correct workspace for visual formatting of printed reports.

Frames are used in reporting tools to group objects together, ensuring they maintain their relative positions during printing. Fields hold data values, links connect objects, and groups organize data but don't control print positioning.

Bursting is the feature that enables delivering a single report to multiple destinations simultaneously. Distributing typically refers to data distribution, broadcasting is one-to-many communication, and copying creates duplicates.

Cascading Style Sheets (CSS) preserve sophisticated formatting when a report is formatted as HTML. Paginating controls page breaks, report properties set metadata, and CSS is the standard for HTML styling.

Lexical references are placeholders for text embedded in SELECT statements in reporting tools. Parameters pass values at runtime, fields display data, and lexical references allow dynamic text substitution in queries.

Anchors fasten one object's edge to another's edge, maintaining relative positions during report generation. Frames group objects, repeating frames iterate over data, and links connect objects but don't anchor edges.

Oracle Reports Builder has five global report triggers: Before Parameter Form, After Parameter Form, Before Report, Between Pages, and After Report. These execute at specific points during report execution.

In Oracle Reports, collapsing anchors are used to suppress the white space that would otherwise remain when an object (like a field or frame) is not printed because it contains no data. This ensures the report layout remains compact and professional.

Boilerplate objects are text, lines, or graphics that appear every time a report runs. Frames group objects, fields display data values, and format refers to styling properties.

The statement 'A cursor is static' is false - cursors can be dynamic depending on the database and configuration. Matrix objects do define relationships between repeating frames, and non-linkable queries contain columns preventing column-to-column linking. Therefore B is NOT true.