Hi,

I do lots of scripting using dw.evaluate()

It work great.

// steen

I implemented this with a new module in my primary application called MULTI-REPORT PROCESSING. It was a major project, but it was worth it in terms of the time saved for the people that generate reports - they LOVE this! It's a generic solution that allows for either the same or different parameters at each run.


It's a Wizard:
   tabpage 1:  Lists all of the available reports and the output options.
   tabpage 2:  List the set of generic parameters that will be distributed to the individual reports
   tabpage 3:  Displays the distributed parameters on each selected report
   tabpage 4:  Everything needed to run the report and specify the target location.

Modules window:


Tabpage 1:


Tabpage 1 with only the selected reports displayed:



tabpage 2:

Note that the parameter values listed above are from SPACES to ZZZZZ.
Check the ALL VALUES checkbox on each row to get the maximum range of the parameter, regardless of datatype.
Valid parameters are saved when the user clicks on the next tabpage.


tabpage 3:

Remember: empty spaces get flagged as errors, but one or more SPACES are valid.


tabpage 4:

Users can specify the target file for the generated reports.
The Max number of rows that can be returned in a report is saved in a Preference (a user-modifiable constant).
Previously selected reports and output options can be overriden here for this run only.
"Halt on error" means to stop the current run on the first error.

Results are displayed by color per row:

it can be done in PB.

i have some lightweight scripting in my app.  I suggest using dw evaluate as much as possible (you need a datawindow object for that but it doesn't have anything in it).   i also have a PB script parser/state machine built to process my functions and parameters.  Simple commands and functions are pretty straightforward.