FastReport support

edited 5:19PM in FastReport 3.0
Hi

Recently I had xls export problems (OLE error) and I searched both forum and the newsgroup. Most of questions about the same problem were without answer. I still don't know if it is possible to create xls file without having Excel installed.

Two months ago I asked on this forum about translating reports using dxgettext. Nobody answered. I didn't get even "Noone use dxgettext" answer. I found myself, that FR3 is not compatible with dxgettext because of TWideStrings class.

Today I try to find on forum how to change in code paper bin. I'm not the first person who try to do it. I couldn't find answer to this question.

Guys, FR3 is a good piece of work. Documentation covers only a part of it (where is documentation for export modules?). Forum is almost useless. How can we solve our problems?

Comments

  • Bert BinnenmarschBert Binnenmarsch Terneuzen
    edited 5:19PM
    Hello Jasiek,
    wrote:
    Two months ago I asked on this forum about translating reports using dxgettext. Nobody answered. I didn't get even "Noone use dxgettext" answer. I found myself, that FR3 is not compatible with dxgettext because of TWideStrings class.
    You can switch languages with the following command:
    frxResources.LoadFromFile('dutch.frc');

    Check out the RES folder of FastReport.

    Bert
  • edited 5:19PM
    jasiek wrote:
    Today I try to find on forum how to change in code paper bin. I'm not the first person who try to do it. I couldn't find answer to this question.
    FR version 3.21.22 has OnPrintPAge event.
    for example:
    procedure TForm1.frxReport1PrintPage(Page: TfrxReportPage;
      CopyNo: Integer);
    begin
    Page.Bin := 1;
    end;
    
  • edited April 2006
    Wow, I didn't expect such answers.
    Bert,
    I didn't try to change engine language, but report itself. Finally I added some limited support for TWideStrings class to dxgettext. Unfortunately, my patch can't be applied to dxgettext, because FR3 uses own TWideStrings class, which is not compatible with TWideStrings from BCB/Delphi.

    Den,
    Do you have some other printing hints? How did you find Page.Bin property? Is it possible for example - to change printing quality?
  • edited 5:19PM
    jasiek wrote:
    Wow, I didn't expect such answers.
    Bert,
    I didn't try to change engine language, but report itself. Finally I added some limited support for TWideStrings class to dxgettext. Unfortunately, my patch can't be applied to dxgettext, because FR3 uses own TWideStrings class, which is not compatible with TWideStrings from BCB/Delphi.

    Den,
    Do you have some other printing hints? How did you find Page.Bin property? Is it possible for example - to change printing quality?
    jasiek wrote:
    Do you have some other printing hints?
    For example:

    Page.PaperSize
    Page.PaperWidth
    Page.PaperHeight
    Page.Orientation
    Page.Duplex

    Do you want change language at run-time or packages language?
  • edited 5:19PM
    wrote:
    Do you want change language at run-time or packages language?

    I'm not sure yet, which one will be more suitable. Now I change language run-time using TranslateComponent() function from dxgettext package. It works pretty nice - it's possible to retranslate strings in application code (cpp and pas files), forms (dfm) and fr3 reports (dfm).
  • edited 5:19PM
    But why you didn't use standard FR functions(frxResources.LoadFromFile('dutch.frc') ;) ?
    FR supports 31 languages.
  • edited 5:19PM
    wrote:
    It works pretty nice - it's possible to retranslate strings in application code (cpp and pas files), forms (dfm) and fr3 reports (dfm).
    Yes, use recompile.exe utility.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.