Hi Drew, > Almost - the report reads the query from disk, so you have to update the > query definition in the odb file before you launch the report.
I admit I was not sure about this detail, so I intentionally omitted it for the moment :-\ > Which > could be looked at as a feature I suppose in that the if you run the > report from the UI later you get the last settings from the form. Not to > mention is you base the original form on the same query...well. Sure, you would a dedicated query just to base the report on, and nothing else. > Another route should be to use the filter settings available at the > report definition. This filter setting is then 'added' to the command > statement used by the report, this should then allows us to base the > report on a query or work just as well if it is based on a table. Then > execute the report without saving the definition and neither the > baseline query and report is altered. I added a mental note that it should be possible to add a filter (or sort, for that matter) to the loadComponentFromURL call for the report. This way, the filter would only apply to this one incarnation of the report - not to the underlying query, not to the report definition. Sounds like it could be useful, /me thinks. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
