If you add a Date range as a Run Time parameter and generate the report using the Task Scheduler the report will stop and await a response.

The easiest work around would be to add the Prior Period date range to the report using the Filters. Then next month change the dates to the prior month and so on.

Can you use the Period Number as opposed to the dates? Because if you can use the Period Number you could add a SQL Where statement to the Container utilizing the @MONTH@ System Variable which contains the current month number and subtract 1 from it.

Run time parameters will indeed halt an automatically scheduled report. Depending on the report, whether a sage 100 worktable (Wrk suffix) or custom report, will determine which route you may need to take. You could use a formula to calculate the prior month start date using the current date or used the month function to return the current month number for the current date and subtract one from it to get the prior "period". There are several ways to do this within the crystal report but if you are trying to modify a worktable report's options and selections in the selection grid, then things get more complicated and you will have to use one of the solutions i've posted to this forum. One details running custom reports added to the sage 100 menu and the other details running worktable reports.

I believe this is a Sage Intelligence report

Good point. I have a bad habit of missing the sub-forum. Saw runtime parameter and just thought of crystal reports.

Good point. I have a bad habit of missing the sub-forum. Saw runtime parameter and just thought of crystal reports.

I hear that