Problems after migrating from 4.22 to 6 & Delphi 6

rbuser

Hi!

We are users of Report Builder 4.22, and now we are working
with delphi 6 and Report Builder 6, and whe have the next problems
in order with the older version:

1. When we put it a data component in the design sheet of the Report,
we don't have any of the field of our tables available.
Sometimes appears the message: Exception in module ...

2. When we acces to the Data sheet appears the message: Acces Violation.

3. When we add a subreport, appears the message: "No Data Pipeline
assigned" with the subreport.

4. The first time we come in to the Report Builder, the trim's don't appear,
we have to close it and come in again. Then appear's the trim's.

5. When we choose a Data option in the Desginer's sheet only appears
one screen to select one DataPipeline. Before we could select two
DataPipeline's, one for the sumary and the other for the main.

6. Appears the Data Sheet but when we choose the Data option we can
not put it a SQL consult.

We have these problems after the migration to the Report Builder 6
and Delphi 6.

How can we solve it?

Thank's.

digitalmetaphors

1. Make sure the datapipeline is set to visible = true.

2. Can you send us your report that is in the 4.22 format, so that we can
trace through the conversion routines to see what is happening.

3. Detail datapipelines are now connected to subreports, not the detail
bands. This change in the architecture makes master detail reporting easier.
The reports should be converted for you by RB.

4. When you say trim, do you mean the rulers that are drawn at the top and
left sides of the designer? This is not a known problem. Can you describe
your system settings and we'll try to reproduce it.

5. Use a subreport in the summary band. Band's can't be connected to
datapipelines, only the subreports can in the current architecture.

6. You can edit the SQL as text once you create a query dataview. Right
click over the dataview to select SQL or go to the SQL tab of the query
designer. Perhaps the width of the dataview isn't wide enough to show the
SQL icon.

Cheers,

Jim Bennett
Digital Metaphors

rbuser

Hi,

1. We use a different Pipelines that we create dinamicly and pass it by
parameter.
One Pipeline for every DataSource. We put it: visible=true for everyone.
But the data's remain not available.

2. This message hasn't appear again. Thank's

3. Ok.

4.Yes, the rulers. If we put the visible property = true of the BDEPipeline
component
we don't have this problem, but then appear's the name of the pipeline in
the options
to choose and we don't want it.

5. Ok.

6. Appears the dataview but, without any tab.

Thank's.

digitalmetaphors

1. When are the pipelines created and set to visible?
2.
3.
4. You shouldn't need to set the pipeline to visible to get the rulers. If
you create a new report from scratch do the rulers appear?
5.
6. Check the Designer.Datasettings.AllowEditSQL property

Cheers,

Jim Bennett
Digital Metaphors

rbuser

Hi

We pass the tables since every form, to one dll, that we use for centralize
all prints.
We pass in one array:

file://Datasource

Tablas_Listados_Confi[k].datasource:=TDataSource(form.findcomponent(componen
te));
file://Tabla

Tablas_Listados_Confi[k].tabla:=TTable(TDataSource(Tablas_Listados_Confi[h].
datasource).dataSet);
file://Nombre Tabla
Tablas_Listados_Confi[k].nom_Tabla:=Nuevo;

And in the 'dll' we assign the parameters to a array.

procedure TEscoge_report.ejecuta(Num1:String;nom1:String;dades2:array of
TDef_Tabla_Rbuilder;B:TBookMark;
Tabla_Principal:TTable;Modo_Help_Param:Boolean;IDU_Param,CDU_Param:STring);

dades:array[1..100] of TDef_Tabla_Rbuilder;

Dades[i].nom_tabla:=Dades2[i].Nom_Tabla;
Dades[i].DataSource:=Dades2[i].DataSource;
Dades[i].Tabla:=Dades2[i].Tabla;

Crear_Report(nombre_fich,Dir);
ppDesigner1.TabsVisible:=True;
ppDesigner1.Showmodal;
FileListBox1.Mask:=Ant_Mask;

In this procedure we create the pipes, and assign the values.

procedure TEscoge_report.Crear_Pipelines;
var
i:Integer;
cadenas:String;
begin
cadenas:=Uppercase(dades[1].Nom_tabla);
i:=1;
while dades[i].Tabla <> nil do
begin
Pipe[i]:=TppBDEPipeline.Create(Escoge_report);
Pipe[i].DataSource:=dades[i].DataSource;
Pipe[i].OpenDataSource:=True;
Pipe[i].Visible:=True;
Pipe[i].Name:=Uppercase(dades[i].nom_Tabla);
Pipe[i].UserName:=Uppercase(dades[i].nom_Tabla);
i:=i+1;
end;
end;

digitalmetaphors

Are the TppField objects getting created on the datapipeline? Access the
FieldCount property to check this. If the visible datapipeline is connected
to the dataset and the report, and the report is connected to the designer
then the designer should be able to show the datapipeline's available
fields.


Cheers,

Jim Bennett
Digital Metaphors