IDE failure to open report designer

rbuser

For a long time now we've been using
ReportBuilder 5 Standard
Delphi 5 Pro
TExtraDevices 1.7
to compile our report libraries (the time investment of verifying *exact
behavioral similarity* for nearly 350 reports was our reason for balking at
upgrades along the way)

We're now making a move away from the BDE by replacing all our TQuery with
TADOQuery which requires (finally) a switch to Delphi6 Pro
ReportBuilder 6.03 Standard
Delphi 6 Pro
TExtraDevices 2.53 (which was originally distributed for D7, but I
followed Waler's instructions for recompilation)

I'm seeing two strange behaviors on mutually exclusive occasions:
(1) Often, when I try to open the report designer by double clicking the
TppReport component, i see a little burst of CPU usage, but then nothing.
Delphi shows "Not Responding" in the task manager, and the GUI is not
repainting. Have to force quit at this point.
(2) When the report designer (occasionally) opens up, it looks like it has
remembered the page size of the report, but none of the components are on
it. If I close the report designer, and reopen it, then the components show
up.

I was under the impression that all one had to do to convert reports to a
new version of RB, was to open it up, and the report designer did all the
conversion. So this is (a) where I suspect the problem is, and (b) where I
hope I haven't missed some critical step in the upgrade process.

thanks for any help,
Matt Regier

rbuser

I have a large number of reports and haven't had any issues in upgrading for
a long time--I remember something vaguely back around version 2

In any case, send a samle report to DM (support@digital-metaphors.com).

Ed Dressel
Team DM

digitalmetaphors

You have RB Pro, so the best thing to do is to try converting the reports at
runtime using the runtime report designer. This way Delphi won't lock up on
you. If you could provide us with a template that shows the conversion
problem you can send it to support@digital-metaphors.com and we can take a
look at it in the conversion process. You can also point your library path
to RBuilder\Source and place break points in the Convert() routine of
TppReport in ppReport.pas when you load a new template to be converted at
runtime to trace through the conversion calls to find out what is locking it
up at runtime.


Cheers,

Jim Bennett
Digital Metaphors