Report wizard not producing any fields RB7.02

rbuser

Hi,

I'm surfacing the end user designed in my application. However, having
stepped throught the report wizard, selecting fields, etc, the finished
report design has nothing in it all; no headings, no data fields. Any idea
what might be going on here?

--
Charles Bainbridge

rbuser

I've just found that the label wizard doesn't do anything on completion
either - no changes to the page layout, columns, etc.

nicocizik

Charles,

There are no know issues with the report wizard. Try recreating the problem
using one of our demo projects. If you still experience the same behavior,
you may have a corrupt install of ReportBuilder. Try reinstalling and see
if that fixes it.

--

rbuser

Another project (the end user reporting example but slightly modified) is
working just fine (I just compiled it), so I don't suspect the installation.

--
Charles

rbuser

I should also add that all the RB components in my project are in a data
module. I notice the design-time designer has a notice about having 'issues'
in a data-module. Could my problem be related?
--
Charles

nicocizik

Charles,

We are unable to recreate this problem here. Try to create a simple example
using one of our demos that demonstrates this behavior and either send the
example to support@digital-metaphors.com so we can take a look, or let me
know the exact steps you took to get the error.

--

nicocizik

Charles,

Move the report component to a Tform.

-------------------------------------------
Article: TppReport and TDataModule
-------------------------------------------

"I've been told not to place a TppReport on TDataModules, but I prefer
to keep my non-visual components on data modules. TppReport is
non-visual, why can't I do that?"


There are two good reasons to avoid placing your TppReport component on a
TDataModule:

1. While TppReport is ostensibly a non-visual component, the components
which make up the report (TppLabel, TppLine, TppMemo, etc.) are obviously
visual. Although the report designer is provided to allow for visual
creation of reports, it cannot be the owner of these visual components.
Therefore, when controls are created during the layout process, they
are given another owner - the form which owns the TppReport (Obviously
the TppReport cannot own them either). The end result of this is that
when laying out a report that is owned by a TDataModule, you are
effectively adding visual components to an object that was never
intended to own visual components. This can result in very unpredictable
results.

2. The TDataModule designer in Delphi 5 was redesigned to include a
treeview which enumerates the various components owned by the data
module and their properties. As a result, when a component that is owned
by the module is modified, the designer recurses all the components
and populates the tree with their property values. When a TppReport is
placed on a TDataModule, many components and properties are added to that
tree. The process of constantly updating these values can tend to cause
a very large performance lag in larger, more complex reports.


--

rbuser

I've moved all the RB components to a form, though not the application's
mainform. I've reinstalled RB. I've deleted the components and re-added them
(well, ppReport and ppDesigner at least) but I still cannot make the report
wizard produce anything. However, if I start a new project, drop a
TppReport, TppDesigner and a TDBISAMDatabase onto a form, set the properties
and off it goes - the wizard generates fields for the report.

What shall I try next...?

nicocizik

Charles,

1. Check all your data settings and make sure they are configured properly
and that your report is connect correctly to a datapipeline.

2. Try connecting your datasources to a DBGrid and see if you are actually
getting data from the database.

3. Try deleting the datapipeline component and replacing it with a new one
on the form.

--

rbuser

Nico,

I don't have a data pipeline component: I'm surfacing the DADE tab and
creating a pipeline with a query. The report wizard 'sees' that pipeline OK.
Once the wizard has closed and left me in the designer (completely empty at
this stage, apart from the default bands), I can add fields from the data
tree and produce a report with no problem.

--
Charles Bainbridge

rbuser

Ok, I think I've finally cracked it. I had assigned a handler to the
designer OnCreateReport event. I did this so I could initialise the designer
form caption to 'New report' when choosing 'new report' or the report wizard
from the designer menu. Otherwise, the designer caption remained set to that
of the report loaded beforehand. This is when the report wizard stops
producing anything. The OnCreateReport event aReport 'var' parameter is nil
when called. I have 'fixed' the problem by assigning my report component to
the aReport parameter.

--
Charles Bainbridge