6.01 Page Size Change Deletes all components + Other Bugs

rbuser

Hello All:

I have noticed some minor IDE "Issues" and wanted to report them as
follows:

1) If I go into the report writer, click on file/page then try to change
the page size, I get a warning message " All components will be deleted ...
". Once that warning is issued, you cannot exit the wizard without deleting
all components on your report.
As a further test, I went into the ppReport properties and manually
changed the report size. In the ppreport component, the change is accepted.
Just do not use the wizard.

2) Occasionally, some glitch occurs which causes a report to "disappear"
in the IDE. I have not yet isolated the circumstances, but it occurred 2
times in a 4 hour session on 2 different reports. What happens is that upon
opening the report, no detail band is showing. Instead, ther is a small
white square ( like a small label ) in the upper left of the IDE ( no
components ). Once this occurs, I can view the .dfm and still see all of the
component definitions, but they and the detail band are not shown.

3) I have a custom component derived from ppTDBText. I can easily add
all I want by selecting it from the toolbar. However, when I use ctrl C,
ctrl V to copy an existing instance of my component, I get an error that
ppNHDBCheck1 already exists. From that point on, the IDE is unstable till I
restart Delphi. In addition, when I view the .pas file, the copied
ppNHDBCheck is listed ( but not shown in the IDE ).
My ppHNDBCheck simply overrides the Function GetTheText and places an X
in the Text if a boolean field is detected with a yes value. ( Function
listed below )
I recompiled from version 5.x to version 6.1 but did not re-write the
routine to mirror the changes made by ReportBuilder in the 6.01 version.


Has anybody else experienced these same issues ???

How soon will ReportBuilder address #1 and #2 ???

Am I doing something wrong to cause issue # 2 ???

Will re-writing my component cure the problem with issue #3 ???


Keep up the great work on this awesome product. We are enjoying alot of
success with the flexibility ReportBuilder provides. Thank you.



Neil Huhta
Profit Monster Data Systems LLC






function TppNHDBCheck.GetTheText:String;
var
lsText: String;
lDataType: TppDataType;
lsFormat: String;
lValue: Variant;
DoTraditionalFormat:Boolean;

begin

if CheckForPipelineData then
begin
try
lDataType := DataPipeline.GetFieldDataType(DataField);
except
lDataType := dtString;
end;

if (Assigned(FOnFormat)) then
begin
lsFormat := '';
FOnFormatIsAssigned:=True;
end
else
begin
lsFormat := DisplayFormat;
FOnFormatIsAssigned:=False;
end;


try
//DataPipeline.GetFieldValue(DataField);
{this will use DisplayValues of the TField}
if lDataType = dtBoolean then
begin
If DataPipeline.GetFieldValue(DataField)=True Then
lsText:='X'
Else
lsText:='';
end
Else
lsText:='';

except on EDataError do
lsText := '';
on EConvertError do
lsText := '';
on EVariantError do
lsText := '';
end; {try, except }

if Assigned(FOnFormat) then
OnFormat(Self, DisplayFormat, lDataType, lValue, lsText);

if FBlankWhenZero and (lValue <> Null) and (lValue=0) then
lsText:='';

end {get data }


else if (Printing) then
lsText := ''

else {must be designing}

begin

{display db field name}
if (DataField <> '') then
begin
if lDataType=dtBoolean then
begin
if DataPipeline.GetFieldValue(DataField)=True Then
lsText := 'X'
else
lsText := '';
end;
end
else {display component name}
lsText := UserName;

end;

Result := lsText;

end; {function, GetTheText}

rbuser

I've certainly experienced (1) - see my posting of 12 Aug
I've also noticed what seems to be another bug - difficult to reproduce, it
only happens occasionally:
Occasionally when dropping a new component on a report, it doesn't get
automatically named -
it appears in the report explorer as just an icon, and you have to rename it
manually.

Roj

digitalmetaphors

1) We've fixed the problem where changing the page size would give the
wanring message, and then delete the components from the band. I'll send
you a patch unit you can use to create reports in the runtime designer,
until we have maintenance release.

2) I personally have had this happen once before when creating a new report,
but could not isolate what could cause it, nor reproduce it.

3) What if you don't override the function in your component, do you still
get a copy-paste error?


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Jim:

Thank you for your response. I probably dont need the patch - Ill just
wait for the release.

When is that release scheduled for ???

I will try to isolate the conditions that cause item #2 to occur. Then
I'll send it on to you.

Neil Huhta

digitalmetaphors

Most likely soon (within the next couple of weeks).


Cheers,

Jim Bennett
Digital Metaphors