Roy,

I found it.
I have been looking at my code and it seems its not too different from yours, except I'm not using the Memo.DataField and Memo.Dataset properties, but the Memo.Text to accomplish the same.
This is my code to add column 'i' to the band:

      Memo := TfrxMemoView.Create(LnBand);
      Memo.Parent    := LnBand;
      Memo.Name      := 'MemoLn' + IntToStr(i);
      Memo.Top       := 0;
      Memo.Left      := x;
      Memo.Width     := w;
      Memo.Height    := hl;
      Memo.Color     := clNone;
      Memo.HAlign    := haRight;
      Memo.HideZeros := true;
      Memo.GapX      := 10;
      Memo.VAlign    := vaCenter;
      Memo.Font.Size := 9;
      Memo.WordWrap  := False;
      Memo.Text      := '[TVal."PVP' + IntToStr(i) + '" #n%2,2n]' ;

Where TVal is the Dataset where the data comes from and PVP1, PVP2... etc.
are the names of the columns to add.

--
Fernando Dias
[Team Elevate]

Fernando


>I use frxXLSExport all the time and I never had problems with it.
>But it seems to me that this issue isn't related to the filter used but with the report itself.

Looking at one of their demos I guessed I had to have a TfrxOLEObject on the form as well. Its the sort of thing that just isn't mentioned anywhere in the documentation. Do you think we could persuade Tim to give them lessons?

Roy Lambert

Fernando


Thanks. I'll try that but I have a sneaky suspicion I'm going to have to use a two (or more) pass report so that I can set the height for each field individually. Unless setting them all to an arbitrary maximum value will work - off to try it.

Roy Lambert

Fernando


Found the solution to one problem - setting StretchMode to smMaxHeight. Another one FastReport say they'll fix in next weeks build - things are improving!

Roy Lambert

Roy,

I'm looking forward to their next build because the current one (9) is unusable, I had to return to build 7.
I still think FR is one of the best reporting tools for Delphi .

--
Fernando Dias
[Team Elevate]

Roy,

> Looking at one of their demos I guessed I had to have a TfrxOLEObject on the form as well.

What for... I never used such an object, and all my reports are exportable to Excel.
Its only needed if you want to embed objects in your report using OLE, like external documents for example.

--
Fernando Dias
[Team Elevate]

Fernando

>> Looking at one of their demos I guessed I had to have a TfrxOLEObject on the form as well.
>
>What for... I never used such an object, and all my reports are exportable to Excel.
>Its only needed if you want to embed objects in your report using OLE, like external documents for example.

I have no idea, but I had ole errors without it but with it the export works. Maybe its the FastReport version, or the Excel version or the weather. I do know I didn't feel like trying to explain to them and get a comprehensible response..

Roy Lambert

Roy,

> I have a sneaky suspicion I'm going to have to use a two (or more) pass report

Do you mean TfrxReport.EngineOptions.Doublepass ?
You don't need that to set column heights... or I'm not understanding what are you trying to do.

Fernando Dias
[Team Elevate]

Fernando


>> I have a sneaky suspicion I'm going to have to use a two (or more) pass report
>
>Do you mean TfrxReport.EngineOptions.Doublepass ?

I did but I was wrong.

>You don't need that to set column heights... or I'm not understanding what are you trying to do.

You sort of do. Their BIFF exporter (or the XLS one) isn't intelligent enough to recognise that when you have one column displaying multi-line text (eg a CLOB column) and another displaying single line text (eg a VARCHAR column) then what you want is just one row NOT one row for the multi-line text and one row for the single line text with an additional empty cell under it filling in the difference in the heights between the multi-line cell and the single line cell.

With a straight print or export to PDF etc it doesn't matter but in Excel it does.

Roy Lambert