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

Self made autosearch screen?

edited April 2009 in Datapipelines
Hello,

Is it possible in the report builder itself (via one of the standaard
events, no external code) to "build" an autosearch screen?

We are using the Report builder integrated in our own program.

We would like to be able to pre-fill the "In List" with all possible
values (existing in the database) before letting the user chose.

Each customer has it's own data, and it can change with time, so we
can't write any fixed values in the search criteria.

If this is only possible through code, do you have an example of a
self made delphi form that can be "called" from the report builder
instead of the standaard autosearch form?

Thanks,

Chantal M.

Comments

  • edited April 2009

    You can define AutoSearch fields and then set the initial value via RAP code
    or Delphi code.

    Example of specifying a list of values for the InList operator...

    myReport.AutoSearchFields[0].SearchExpression := 'value1, value2, value3';

    The RB 11 Parameter enahancements also enable you to define a LookupList of
    values.



    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited April 2009
    Thanks,
    We are still using RB 10.
    Where can I find documentation or examples on how to do all of this
    with RB11?
    So that I can see if it's worth it for us to upgrade?

    Chantal

    On Thu, 9 Apr 2009 10:24:03 -0500, "Nard Moseley \(Digital
  • edited April 2009

    Here is a list of What's New in RB 11, you can use the side menu to navigate
    to more detail. Trial versions are available for download from our web site.

    http://www.digital-metaphors.com/rbWiki/General/What's_New/RB_11


    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.