Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Frequent regeneration of preview from code

edited January 2002 in General
In an existing non-RB application of mine, the user may quickly generate
certain standarized documents by making choices from particular menus, and
by filling out a few fields in a form. The program will then create the text
and graphic elements that make up a page, positioning everything
automatically. Until now, I have used a bitmap canvas to preview that page
on the screen, giving a running impression of how the result will look.
There are also some printing options.

But now of course I want to use RB for this process, adding elements
programmatically to a hidden RB report, and using the RB viewer to show the
user what is going on.

Are there any problems with the constant regeneration of the preview, in
response to user typing and choices? Will there be a problem with
flickering? Any experiences with this approach?

Mvh/regards
Svein Olav Mytting
Intelligent Software AS
Bogstadvn 60A, 0366 Oslo

Comments

  • edited January 2002
    The report generation is dependent on how fast it can open the dataset.
    First, create a small dataset so you'll get a good single page
    representation, and then you can set the Report.PageLimit to 1 so that it
    will only print a one page preview. If the report is a single page, and the
    Report.PassSetting is set to psOnePass, then it should generate quickly.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.