Crosstab Wizard Doesn't Show at Runtime

rbuser

Is there a way to have the crosstab wizard available for users at runtime?
It shows up at design time but not at runtime. thanks, LL

digitalmetaphors

Add ppCTWiz to your uses clause to register the crosstab wizard at runtime.

--
Cheers,

Alexander Kramnik
Digital Metaphors

rbuser

that makes it show up just fine ... thanks very much ... however the report
now seems to get into an endless loop when we preview it ... any
suggestions? thnanks, LL

digitalmetaphors

Here's some guidelines that might help you pinpoint the problem.

--
Cheers,

Alexander Kramnik
Digital Metaphors

------------------------------------------------------
Article: TroubleShooting: Report Prints Endless Pages
------------------------------------------------------

Occasionally, we have customers state that their reports are in some
infinite state where page after empty page prints forever.

There are a few items to check when this occurs.

The TppReport.AutoStop property is the first thing to check. If this is
false when the DataPipeline property is unassigned, the endless report will
be the result. AutoStop is automatically set to True when DataPipeline is
set to nil, but it is possible to set it back to False. Check for instances
in your code where you might have created this condition.

Another thing to check is that all subreports in your report have their
DataPipeline set. When a subreport does not have its pipeline set, you will
sometimes see a condition where the first detail record prints and then you
get blank pages.

Another, non-data related cause can sometimes be your margin settings. If
you have stretching bands that need to overflow to the next page, if your
margins are too tight, sometimes the report engine will endlessly overflow
to the next page trying to fit the overflow material. As a test, try setting
DetailBand.PrintHeight to phDynamic. A dynamic height band can overflow to
additional pages as needed.

Still another cause might be having a statically positioned control, set to
ReprintOnOverFlow, in the same band with a stretching control. For instance,
if you have a memo set to stretch and in that same band, a label control set
to ReprintOnOverFlow, then on every page after the first, the memo will
begin to print after the label control. If the label is placed low enough
that the memo has no room to print, the report will forever be trying to
print the overflowing memo on the next page.

rbuser

We checked everything in the white paper you sent us but we are using only
the design application (with really very little code) as described in your
tutorial "Building an End-User Reporting Application). We added the ppCTWiz
unit as you instructed so we could design a crosstab at runtime but we seem
to get the loop on a Crosstab Wizard report and the Caption "Calculating
Crosstab: Record ... " is repeatedly displayed at the bottom. We don't seem
to have this looping problem with DBISAM tables ... only Paradox ... any
suggestions? thanks, LL

digitalmetaphors

Do non-crosstab report run agains Paradox? What are you using to connect to
the database, BDE? BDE can be relatively unstable though it does work with
RB. Try running a simply report against Paradox. If that doesn't work the
problem must lie with the DB drivers. If it does, then add the crosstab.
Don't forget to assign a pipeline to the crosstab. You can also try the
Paradox demos in RBuilder\Demos\End User Databases to see if you can
successfully compile and run those.

--
Cheers,

Alexander Kramnik
Digital Metaphors