![]() ![]() In this configuration Base collects the user-files generated by both Base and HSQLDB, and stores these files within a single ODB file. Bundled database options include: spreadsheets ( flat-file datasets), dBase tables ( DBF), and a relational database engine ( HSQLDB) featuring SQL.įurthermore, Base creates an "embedded database" by default utilizing the bundled HSQLDB engine. This can give the impression that Base, itself, is providing the back-end database functionality. ![]() In fact, a Base form can be exported as standalone Writer document.Ĭonfusion lies in the fact that *Office is also bundled with various "back-end" database options which connect seamlessly with Base. And while Base is typically used to create forms in the *Office environment, note that all Form elements (form 'controls' such as table grids, list boxes, navigation bar, etc) are available in Writer and Calc, complete with access to all registered data-sources. These graphical elements in Base are provided through various wizards or visual designers including: a Table Designer, Query Builder, Form Designer, Report Designer, and Integrated Macro Development Environment ( IDE). Base, itself, can be used to view and manipulate the data, generate stored queries or views, create forms, reports, and macros. Data analysis becomes possible with Calc through charting and pivot tables (Data Pilots). You can also add dynamic tables or query-views to a Writer document or Calc spreadsheet utilizing registered data-sources. For instance, a registered data-source can be selected in the Mail Merge Wizard within Writer, allowing the creation of mailing labels or form-letters. In this primary role, Base is used to create the necessary connection file (ODB), which can then be 'registered' in *Office for universal data-access from Writer, Calc, etc. Base is merely a front-end, used primarily to connect *Office ODF documents to various data-sources including tabular spreadsheets, address books, dBase tables, or relational databases. It involves separating the graphical user-interface (GUI front-end) from the core database functionality (database engine back-end). This two-tiered software model provides flexibility and the necessary data-durability. Database applications often incorporate separate " front-end" and back-end components. 8.5 Why is searching in my form/table so incredibly slow?.8.4 Why does my table show the wrong number of records?.8.3 How are my Address Book fields mapped to columns?.8.1 I can access my tables with *Office, but I can't update or insert any data - why?.7.1 How do I create a form with a sub form?.6.1 How can I import a spreadsheet table to a database?.5.2 Why can't I delete a record in my dBase Table?.5.1 How can I, in dBase, create queries for more than one table?.3.9 How do I determine which version of HSQLDB is in use with Base?.3.8 How do I setup multi-user 'server mode' access to my HSQL database?.3.7 How do I edit the Field properties of a 'split database' Table ?.3.6 How do I convert an "embedded database" to a "split-database" ?.3.5 How do I create a new 'split' HSQL database using Base?.3.4 How do I setup support for 'split' HSQL databases in Base?.3.3 So why should I avoid 'embedded databases'?.2.2 Why can't Base load/find my JDBC driver?. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |