Re-Running a report

[Alaska1]

I have created a report with parameters. It is pulling date, location, etc. I am going to need to run the report for several divisions. How can I keep running the report without closing it. Is there a way to refresh so I can add in a new date, location?

[RuralGuy]

Are you trying to get all of the division reports in one report?

[Alaska1]

Are you trying to get all of the division reports in one report?

No, they are separate reports. I do not want to have to close the report and re-open it everytime I run new parameters. I am going to be running data by division and area.

[RuralGuy]

You can automate the opening and closing of the report so I don't think I understand the problem. Are you using a form to provide the parameters?

[Alaska1]

You can automate the opening and closing of the report so I don't think I understand the problem. Are you using a form to provide the parameters?

No, using parameters in the query.

[RuralGuy]

A query can easily pull its parameters from a form. Have you looked into using a form to automate the process?

[Alaska1]

A query can easily pull its parameters from a form. Have you looked into using a form to automate the process?

I am tried created a form with drop down boxes to run the parameters in the report. I cannot get it to work. I tried using the code below

First, create a query that will display the fields you wish to show in
the report.

Second, create a report, using the query as it's record source, that
shows the data you wish to display for ALL records.

Using Clerk_ID and Assigned Clerk field.

Created a new unbound form.
Add a combo box that will show the Clerk_ID as well as the
Assigned Clerk field .
Set the Combo box's Column Count property to 2.
Hide the Clerk_ID field by setting the Combo box's ColumnWidth
property to 0";1"
Make sure the Combo Box Bound Column is the
Clerk_ID.
Name this Combo Box "cboclerks".

Add a command button to the form.
Code the button's Click event:
Me.Visible = False

Named the form "Form1"

Go back to the query. As criteria, on the Query's Clerk_ID field
criteria line write:
forms!Form1!cboclerks

Code the Report's Open Event:
DoCmd.OpenForm "Form1" , , , , , acDialog

Code the Report's Close event:
DoCmd.Close acForm, "Form1"

Run the Report.
The report will open the form.

Find the Assigned Clerk in the combo box.
Click the command button.

I am still trying to get this to work.

[RuralGuy]

I would simply set the RecordSource of your report to your query. Then run the report from the form, either from a button or the AfterUpdate event of the ComboBox. Use the acDialog argument of the OpenReport command to stop the form code until the report is closed.

[Alaska1]

I would simply set the RecordSource of your report to your query. Then run the report from the form, either from a button or the AfterUpdate event of the ComboBox. Use the acDialog argument of the OpenReport command to stop the form code until the report is closed.

Thank you for all your help. If I create a comman button on the form to preview the report should I use the code below.

DoCmd.OpenReport Forms!frmOpt.Form!RunName.Caption, acViewPreview.

[RuralGuy]

DoCmd.OpenReport "ReportName", acViewPreview, , , acDialog
Do you think that Forms!frmOpt.Form!RunName.Caption points to a ReportName?

[Alaska1]

No, Sorry copied script. I meant to change it.

[RuralGuy]

Where does that leave us? Have you got it working yet?

[Alaska1]

Where does that leave us? Have you got it working yet?

I am going to try it later. Thank you for all your help. I will try it this way.

[RuralGuy]

I'll be around.

[Randy]

I'm having a similar problem. I have a report that uses a query to get its data and I have a form setup to enter the data (paramaters for the query) with a button that runs a macro that opens the report. The strange thing is, I have another report setup like this that runs fine but the new report only previews an empty report.

Are you aware of an example on the internet that I could take a look at. I've studied my working report to death but can not figure what is wrong.

Thank you,
Randy