On Thu, 2012-03-29 at 16:40 +0100, Tom Davies wrote: > Hi :) > Blimey. i hadn't really appreciated that about Base. Sounds like it might > be reasonably easy to let people have access to some of the data in the > database while still keeping other data confidential. So different users > could have access to different fields. > > These Odt's and .Rpt's can appear to exist outside Base? So people just see > an Odt file without really being aware they are using a database?
yes and no. In the case of a form developed within a Base file - if you open it in data entry mode and save it as a stand alone text document it will loose all links back to the datasource - these can be fixed up of course. This then brings up another difference, in a stand alone ODT/ODS file embedded dataform components may be attached to multiple datasources. This is disallowed when embedded in an ODB, all dataform components must connect to the same datasource. In the case of a Report Wizard (no Report Builder installed) created file, saving it as a stand alone ODT file will create ONLY a static report - in other words the values will be static. There is mechanism for running the report again - though all the information required to do so is contained within a set of hidden controls in the document, the code to execute them as needed is not available outside of the Base module, nor is there an api for calling it directly. In the case of a RPT definition created with Report Builder, there is no way to work with that outside of the Report Builder extension. In the case of scripting there are also some differences. A stand alone ODT/ODS may have scripts embedded within in the document, this is not allowed when the document is itself embedded in an ODB file, rather embedded scripts must be stored at the ODB level. If you have any scripts that make use of the ThisDatabase pseudo variable those would break as this variable is, naturally, only valid when the script is loaded from an ODB file. //drew > Regards from > Tom :) > > --- On Thu, 29/3/12, drew jensen <drewjensen.in...@gmail.com> wrote: > > From: drew jensen <drewjensen.in...@gmail.com> > Subject: Re: [libreoffice-documentation] Clarification on "Text Documents" > To: documentation@global.libreoffice.org > Date: Thursday, 29 March, 2012, 16:25 > > On Thu, 2012-03-29 at 11:12 -0400, Dan Lewis wrote: > > Specifically, LO uses Writer to create forms for Base. Seems to me > > that what Writer creates is "text documents". If not, then what is a > > Base form? Is it a document? If so, what kind? > > Yes - it is a standard ODT document. > > The differences the user sees at run time, per what is and is not > available in UI and what parameters are pre-loaded is done by code, > triggered when the form is loaded from within an ODB file. > > Depending on how the document is opened, for editing or for data entry, > it is treated as either a OTT or ODT. > > Report made with the default Report Wizard (meaning when there is no > Report Builder installed) are also standard ODT files. > > Report Builder report definitions are not standard ODT files they are > RPT files, which is a variant of the ODT file structure. When a Report > Builder definition is used to generate an actual report then this output > is either a standard ODT or ODS document. > > I hope that helps, > > //drew > > > -- > Unsubscribe instructions: E-mail to documentation+h...@global.libreoffice.org > Problems? > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/global/documentation/ > All messages sent to this list will be publicly archived and cannot be deleted > -- Unsubscribe instructions: E-mail to documentation+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
