Setting report parameters at run time

[smrogers]

Hi,

I have a basic report (just a list of clients). The OnPrintInit event runs an Action Script, which displays an X-Dialog box giving the user a choice of three different parameters for the report:

Sort by Code, where the "Exclude" logical field is set to .F.

Sorte by date added to the database, where the "Exclude" logical field is set to .F.

Sort by Code, where the "Exclude" logical field is set to .T.

If I run the various saved queries on a form for the database, I receive the expected results.

However, when I run the report, the last querey that was run is used, regardless of what is selected when the X-Dialog is launched from the OnPrintInit event.

I'm clearly doing something wrong -- what's the best way to present the user with a preset list of sorting/selection options when running a report?

Any help would be greatly appreciated.

[Tom Cone Jr]

Re: Setting report parameters at run time

Pass the filter expression to the report when the report is called. Here's an example from the help file:

PRINT_REPORT("Invoice", "Invoice_Number > " + quote("000001"), "Date")

[Stan Mathews]

Re: Setting report parameters at run time

I have a basic report (just a list of clients). The OnPrintInit event runs an Action Script, which displays an X-Dialog box giving the user a choice of three different parameters for the report:

- does the xdialog actually do anything aside from asking for the parameters? If so, what?

However, when I run the report, the last querey that was run is used, regardless of what is selected when the X-Dialog is launched from the OnPrintInit event.

- correct behavior if your report is set to print current selection of records.

I'm clearly doing something wrong -- what's the best way to present the user with a preset list of sorting/selection options when running a report?

- base the report on current selection of records, prompt the user for desired parameters, query the table or set upon which the report is based, voila.

As an alternative to querying the table, you can use

report.print("reportname", "some_filter_expression", "some_order_expression")

[smrogers]

Re: Setting report parameters at run time

Tom,

How do I give the user a selection (i.e. maybe a Drop-Down list) of sort criteria using the method you mention? Right now, I have a "Main Menu" form with a button that says "Reports". That button in turn gives a selection of reports using "ui_popup_menu" (something I found in the help files). Should the selection then launch an X-Dialog box box giving the user their choices, which would then in turn run the code you listed above? Thanks...

[smrogers]

Re: Setting report parameters at run time

Stan,

Your solution looks much like Tom's... I guess it's the logistics where I'm getting lost...

Maybe I'm over thinking this -- let me rephrase the question a bit: Where should I give the user a choice of parameters, and how should that be done? Is OnPrintInit the proper place? Or should it happen when a "Select Reports" button is pressed?

Thanks again for the help guys...

[Tom Cone Jr]

Re: Setting report parameters at run time

I think OnPrintInit is too late and would follow this kind of sequence:

a) user selects report
b) if report can accommodate user selectable filter or sort order get input from the user
c) run the report with filter and ordering expressions to suit

To do this the report layout must not have any embedded filter or ordering expressions and should not be tied to any earlier view of the set or table involved in the report.

-- tom

[Stan Mathews]

Re: Setting report parameters at run time

I think OnPrintInit is too late and would follow this kind of sequence:

a) user selects report
b) if report can accommodate user selectable filter or sort order get input from the user
c) run the report with filter and ordering expressions to suit

To do this the report layout must not have any embedded filter or ordering expressions and should not be tied to any earlier view of the set or table involved in the report.

-- tom

My thinking concurred with Tom's until I went back to the documentation.

You can use the OnPrintInit event to prompt the user for variables by opening a form as a dialog, or by using a UI_GET_TEXT() function, or by running an Xdialog box. These variables might then be used in the report's filter and order expression (defined in the report's Detail properties). IMPORTANT: The variables that you prompt for in the OnPrintInit event must be DIMmed as "shared" or "global". For example, the following Xdialog box prompts for the state. The report filter then has the filter expression: "state = var->whatstate".

It sounds as if the report in question is not set up this way.

[John Gamble]

Re: Setting report parameters at run time

Here is a solution I use throughout my app.

Autoexec Script:

Initialize the variables (Global) you will use in the x-dialog box.

Eg: Beg_Date = {}
End_Date = {} etc.

Push button on form:

1. Display an x-dialog box to allow the user to input various parameters.

2. Set any required variables. e.g.
If End_Date = {} set End_Date to Beg_Date.
(Allows user to input 1 date only.)

3. Print report with record selection e.g.
If Beg_Date <> {} then
Beg_Date => var->V_Beg_Date .and. End_Date =< Var_V_End_Date.
Else
Select all records.

The original x-dialog box was generated using action scripting & modified accordingly.

See attached x-dialog screen shot.

John