Problem with old Reports, ported from 4.21 to 6.03

rbuser

Hi!

I ported old reports from version 4.21 Delphi 4 to 6.03 Delphi 6.03.
Report consists of only detail band. DataPipeLine connected with dBase
table. Table has only
one record. I want to print only one page (Payment order blank). In Preview
form i see only one page. When i realy print, both from Preview form or from
program code, i get first page with 60% of blank and many empty pages.

Printer work good, theare no problem with old version of my program.

Best regards,
Pavel Stepanov

digitalmetaphors

There was probably a problem wit the conversion of the datapipeline
assignemnt. The architecture changed in that the detail band cannot be
connected to a data pipeline. You should connect the Report.Datapipeline
property. If you have subreports, also make sure to set the subreport's
datapipeline.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Who can help me?

It is always a good idea to have the latest printer drivers.

You should be able to run both versions of ReportBuilder in different
verions of Delphi. ReportBuilder will install itself in the appropriate
Delphi directory and thus should not confict with different versions of
itself since they are located in in different places.

Cheers,

Alexander Kramnik
Digital Metaphors

----- Original Message -----
From: Stepanov Pavel
To: Alexander Kramnik
Sent: Thursday, April 04, 2002 4:34 AM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


Hi,
Alexander!

I completly uninstal all version of RB and then reinstal RB 6.03 for D5

No nothing help me!

I have Delphi 5.0(Build 6.18) Update Pack 1, Windows 98 (Build 4.10.2222 A),
network printer HP LaserJet 4000 Series PCL 6.
Printer Quee format is RAW, print after first page ready.

I try send report to another network printer - HP LaserJet 2200 Series PCL
6.
I get stable AV!!! Testing print from the Word work fine. My old application
print to HP 2200 wthout problems too.

It's remember me situations with old versions of standart Quick Report. It
was wery unstable
product, unlike ReportBulder 4.*!

Is it realy true, that the last version of RB works only with the newest
version of drivers?
Will i need to reinstall the newest drivers for all my clients?
Which printers now unsupported by RB?
What is last stable version of RB?
I very discouraged by the newest version.

It seems to me, the problem is in automatic conversion my old reports to new
format or in Reports Engine.

Next question,
how i can use version 4.23 in d4 an 6.03 in d5 simultaneously?
When i must place files from C:\Windows\system ?

Cheers,
Pavel Stepanov.

----- Original Message -----
From: Alexander Kramnik
To: Stepanov Pavel
Sent: Monday, April 01, 2002 11:18 PM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


I ran the project here and was able to preview and print successfully. I get
a single page report in either case. Please make sure that you have the
latest printer drivers for your printer. If the problem persists, please
send a sample project with just one report on it that reproduces the problem
to support@digital-metaphors.com. One other thing to try is to completely
reinstall ReportBuilder using the following guidelines to make sure you are
not using any RB 4.21 libraries.

--------------------------------------------
Article: Cleaning up a Corrupt Installation
--------------------------------------------

If you have been advised by Digital Metaphors technical support that you may
have a corrupt installation, or if you are having difficulty installing,
compiling or running applications after a ReportBuilder install, then it may
be necessary to manually remove all ReportBuilder files from your system.
Corrupt installations usually result when you are installing over a previous
version of ReportBuilder which was not installed into the default directory,
which was recompiled from the source, or when ReportBuilder files were
manually moved from the default install location. Cleaning up a corrupt
installation, consists of locating all ReportBuilder related files, and
deleting them from your system. The first step is to use the uninstall
program to remove as much of ReportBuilder as possible.


Run the uninstall program

1. Exit Delphi, and all other applications. You should have no applications
running except the uninstall, otherwise you may lose some of your work.

2. Select Start | Settings | Control Panel from your Windows desktop.

3. Double-click the Add/Remove programs icon.

4. Locate the version of ReportBuilder you wish uninstall and double-click
it.

5. The first page of the Uninstall Wizard allows you to choose between an
Automatic or Custom uninstall. Choose Custom and click the Next button.

6. Click the Select All button, then the Next button. Repeat these steps
until you reach the last page of the wizard.

7. Click the Finish button. All of the items you selected will be removed
from the system.

8. After all the ReportBuilder files are removed, you may be prompted to
reboot the system. If this is the case, reboot the system.


Delete the ReportBuilder root directory (and all subdirectories)

1. Using the Windows Explorer, locate the ReportBuilder root directory. The
default directory is:

C:\Program Files\Borland\DelphiX\RBuilder

2. Once you have located this directory, inspect it. If you have any custom
work in this directory which you would like to keep, move it to another
directory.

3. Delete the ReportBuilder root directory.


Delete all remaining ReportBuilder files

1. Using the Windows Explorer, search the entire hard drive for all
occurrences of:

dclRB*.bpl
dclRB*.dcp
rb*.bpl
rb*.dcp

2. Delete any occurrences which correspond to the version you are removing.
All packages are named with the convention NN, where the first number
is the ReportBuilder version and the second number is the Delphi version.
Thus, a typical package name for Delphi 5 would be rbRCL45.bpl. The same
package for Delphi 4 would be: rbRCL44.bpl. Check Installing ReportBuilder
for a list of the packages associated with each version.

3. Using the Windows Explorer, search your hard drive for all occurrences
of:

pp*.*
da*.*
ra*.*

4. These are the prefixes used by individual ReportBuilder units. 'pp' is
used for ReportBuilder units, 'da' is used for DADE units, and 'ra' is used
for RAP units. Depending on which ReportBuilder you have (Standard,
Professional or Enterprise) you may not have all of these unit types.



Additional Notes

1. Never have Delphi running when installing ReportBuilder.

2. All ReportBuilder related files should be stored in the root directory
$(DELPHI)\RBuilder.

3. All ReportBuilder run-time packages should be stored in the
Windows\System directory.

4. You should never have ReportBuilder files in Delphi\Lib, Delphi\Bin or
Delphi\Projects\Bpl.

Cheers,

Alexander Kramnik
Digital Metaphors
----- Original Message -----
From: Stepanov Pavel
To: Alexander Kramnik
Sent: Sunday, March 31, 2002 8:23 PM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


Hi,
Alexander!

I send to you selfextructing archive with executable file end projects
source.
You should install it in C:\TestReport\ or edit one line Main.pas.

procedure TMainForm.Button1Click(Sender: TObject);
var taPR001_Version : Integer;
begin
DmMsg.taPR001.Close;
DmMsg.taPR001.DatabaseName := 'C:\TestReport\Base'; //!!!!!!!
DmMsg.taPR001.TableName := 'k0000341.dbf';
...

Cheers,
Pavel Stepanov.


----- Original Message -----
From: Alexander Kramnik
To: spd@irvtb.ru
Sent: Saturday, March 30, 2002 4:29 AM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


Please send the source to your project so we can debug it.

Cheers,

Alexander Kramnik
Digital Metaphors----- Original Message -----
From: Stepanov Pavel
To: Alexander Kramnik
Sent: Thursday, March 28, 2002 9:10 PM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


Hi,
Alexander!

I done sample project.

In preview all OK, but when i push Print button - i get empty pages.

Pavel Stepanov.

----- Original Message -----
From: Alexander Kramnik
To: spd@irvtb.ru
Sent: Friday, March 29, 2002 2:07 AM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


Please see if the information below can help resolve your issue. If not,
please send a sample project that reproduces the problem.

------------------------------------------------------
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 enoug

Cheers,

Alexander Kramnik
Digital Metaphors

----- Original Message -----
From: Stepanov Pavel
To: Alexander Kramnik
Sent: Thursday, March 28, 2002 12:46 AM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


Hi,
Alexander!

Sorry for mistake, i use ReportBuilder Prof 6.03 in Delphi 5.

I have 10 reports in DataModule. For previewing report i use procedure:

procedure PreviewPrint(Report : TppReport);
begin
Report.ShowPrintDialog := True;
Report.AutoStop := True; //Report.AutoStop := False; no matter- true or
false or absent!!!
Report.PrinterSetup.PrinterName := 'default';
Report.DeviceType := 'Screen';
Report.PrinterSetup.Copies := 1;
Report.Print;
end;

In PreviewForm i see only one page with all elements - like i want.
But when i push "Print" button first page printed not completly and i get
blank pages.

Missing elements from right sede of page near upper right coner an elements
in second
half of page.

I have not subreports and regions.

DetailBand.PrintHeight is phDynamic!

In DmReport.dfm not found property "Stretch","Shift*"

When i open reports in designer, i see message:
"There are known issues with using the Report Designer at Delphi desigh-time
for reports
residing on a TDataModule. You may experience instability and slow
performance"

Should i reside Reports in simple autocreate Form with Visibele := false; ?
Whats type of "istability" do you mean?

If you can't to help me, i will send demo project later. My projects large
and with non standart
components (not report components) and i need a lot of time to do simple
example.

----- Original Message -----
From: Alexander Kramnik
To: spd@irvtb.ru
Sent: Wednesday, March 27, 2002 11:36 PM
Subject: Re: Problem with old Reports, ported from 4.21 to 6.03


If the following article does not help solve your problem, please send a
sample project that reproduces the problem to support@digital-metaphors.com.
------------------------------------------------------
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.

Cheers,

Alexander Kramnik
Digital Metaphors

----- Original Message -----
From: Tom Ollar
To: Alex Kramnik
Sent: Wednesday, March 27, 2002 7:52 AM
Subject: Fw: Problem with old Reports, ported from 4.21 to 6.03



Cheers,

Tom Ollar
Digital Metaphors Corporation
----- Original Message -----
From: Stepanov Pavel
To: support@digital-metaphors
Sent: Wednesday, March 27, 2002 3:25 AM
Subject: Problem with old Reports, ported from 4.21 to 6.03


Hi!

I ported old reports from version 4.21 Delphi 4 to 6.03 Delphi 6.03.
Report consists of only detail band. DataPipeLine connected with dBase
table. Table has only
one record. I want to print only one page (Payment order blank). In Preview
form i see only one page. When i realy print, both from Preview form or from
program code, i get first page with 60% of blank and many empty pages.

Printer work good, theare no problem with old version of my program.

Best regards,
Pavel Stepanov