What release of SQL Developer do you use? Unless it is a very old release, you should be able to run the report once and export the report output to a PDF file. Just right-click on the results tab, select Export..., and pick pdf from the Format drop-down list. Control formatting from the Edit Report dialog, Note the PDF node under the Master Report node, with lots of options to control layout, headers and footer, etc.
In general, opening a report from the Reports view will execute that report. The report results tab's toolbar has a Refresh timer setting, with a default of 0 to avoid refreshes.
Hope this helps,
SQL Developer Team
I do have the Refresh set to 0. I don't want to export to PDF yet because I am still editing the various SQL queries within the report, but my work is slowed by the constant refreshes, which happen whenever I open the report and whenever I click Apply after making a change. Refreshes also seem to happen when navigating within a master report with multiple children.
I have version 220.127.116.11, which I believe is the latest.
Have you considered not editing / testing / refining all those queries in the Report editor? Due to the editor being modal (one must exit it in order to do anything else), I prefer to develop and test code in a worksheet. That way I can take advantage of features such as code completion insight, access to the object viewer to review the metadata and/or data of objects used in the reports, the SQL Tuning Advisor, and so on. Then copy/paste the code into the report when ready.
Even if coding directly in the report editor, one can select Edit without selecting Open first, and moreover can Edit without selecting a specific connection. Editing (or copy/pasting) multiple child queries can be done without hitting the Apply button in between. Any combination of these techniques will avoid slow downs due to executing (or re-executing) queries. Hope this helps...