On Fri, 2012-01-06 at 16:50 +0100, Reizinger Zoltán wrote: > Hi Dan, > > I was the community volunteer QA who helped the report builder > developer, to remove bugs from the application. > > You can create static report with report designer only when you use the > report wizard. > > In design view no option to run report as static report. > > The static report was no question, during times when I participated in > report builder development. > No issue/bug was opened on it. > > Regards, Hi Zoltan
I think this is a case where the term doesn't carry over from the one tool to the other. In the case of the Report Wizard you can save the results into the ODB wrapper and then when it's opened next you need to have designated whether it will be treated as a template or document. If template the report definition saved in the hidden fields is re-run, in the case of the document (static report) it is simply opened. In the case of the Report Designer an actual report definition, as a unique type, is introduced. So after running a report definition you create the equivalent of the Wizard's static report simply by saving the ODT or ODS file generated. When you execute a save function in the Designer interface you are always saving only the definition back into the ODB wrapper. I hope that helps, //drew > > 2012.01.06. 15:55 keltezéssel, Dan Lewis írta: > > The report wizard in both OOo and LO gives a choice of a static or > > dynamic report. Where is this choice in the Report Builder? I can't find > > it. Or, has it been decided that a static report no longer serves a > > purpose? > > I know that limitations can be placed upon the query or view upon > > which the report is based. This might take the place of a static report. > > But would this always be the case? I don't know. > > Example: a report shows an abnormality. After this is corrected, > > data is modified in the database. Run the report again, and the > > abnormality might disappear. Where is the proof that the abnormality > > every existed? Just a thought. > > This is going to both lists in case someone from one of them knows > > the answer. > > > > --Dan > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
