![]() Optionally, you may use queries to limit the output and you may use more or less advanced tools for report creation. This office suite is just an additional option for database output among others. Input and maintenance of content is managed by some other tool. Database creation has been done by means of some other tool. This requires read-access to the underlying source of data together with slightly advanced end user skills, making Base an extremely useful part of this office suite because you can access your data beyond the limitations of supported file formats. Stage 1: Access tabular data from almost arbitrary sources and serve them to Writer and Calc for pretty printing, spreadsheet analysis, serial letters, pivot tables, charting and many other things. Base utilizes office documents to present database contents and form controls.įrom my personal point of view, Base can be used in 3 stages This old-fashioned, document-oriented desktop software has nothing in common with web-based database frontends, as used in web-shops or exposing this forum's database. You can use a database frontend to create something which finally (and hopefully) can be used easily by an assumed end user, so it's a development tool. ![]() Please understand that tools like Base, even the better ones, are not made for "the end user". Even the native, self-contained database which can be generated from scratch is not what it seems to be.īecause Base is so generic by intention, you can not do much with it unless you understand some fundamental concepts of database development which apply to most databases on the market. There is just a collection of software tools to connect Writer and Calc with a wide variety of tabular data sources. There are spreadsheets for everything, but no dbs at all. I am surprised that there isn't a simply db for oo that isn't web based. MSworks has a basic DB program that is a piece of cake to use. There must be something I just don't understand. Kaustein wrote:It was web basis and it didn't work. In the meantime, however, a Writer document reading data from a Calc spreadsheet can be made to reproduce a Works DB and is good experience for transfer later to Base. In due course you may need to copy the data from the Calc spreadsheet into a Base table and recreate a Base form that will permit entry and edit of the source data. There is a limitation to this method in that any changes or additions to the database can only be entered in the spreadsheet. You may find these two sources helpul guides: To reproduce the Works "form" (f9), create a new OOo Writer text document and use its "mail merge" abilities to create the layout of your Invoice Form. You will need to insert a new first row in which to type the field names that will not have copied across. Until you have gained experience with the potential of OOo Base, you may find it easier to copy the Works data from its "list view" (Shft+f9) and paste it into a new OOo Calc spreadsheet. ![]() It is ultimately rewarding in that Base will give you more flexibility and scope, but you may find as an intermediate step that a combination of OOo Calc and OOo Writer more readily replicates the MS Works DB which is essentially an interaction between the Works spreadsheet and word processor. The structure of OOo Base differs significantly from Works Db, and I found the conversion learning curve quite steep. ![]() If you are trying to convert from a MS Works invoice DB, I would recommend a step by step approach. With ms works you created the fields, defined what you wanted them to do, and then moved them about the form to create the DB, but I just can't seem to figure out even how to get started that makes sense. But with OO, it is very hard just to start. I have used ms works in the past with absolutely no problem. I am having one heck of a time in trying to create an invoice DB for my small service company. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |