42 Grafton Street, Dublin 2, Ireland
+353 1 611 5607 · info@break.ie
Monday to Friday, 9:00 AM to 6:00 PM
LibreOffice Base Guide
This LibreOffice Base guide explains when Base helps and how to use it for forms, queries, and simple database tasks. Base is a database front end inside the LibreOffice suite, not a separate product you need to buy. It suits small-office record keeping where a spreadsheet has become hard to search or update safely.
One sheet at a time, the task gets done
A client list, a parts catalogue, or a loan register has records with fields that repeat. Base stores each record once and lets you view it through forms and queries. That structure prevents the same client appearing under three spellings. A spreadsheet can hold such data, but Base makes relationships and required fields more explicit.
Think of the moment a list stops being a list. You need to find a client quickly, check what was ordered, and add a new order without retyping the address. That is the point where a table, a form and a query do calmer work than another column.
Jump to a sheet
Use these tags to move through the pile in the order you would build the database: table first, then the form people use every day, then the questions you ask of it.
A table in Base holds one kind of record, with columns for each field. You define field names, data types, and whether a field may be left empty. A primary key gives each record a unique identifier. Keep one kind of record per table: clients in one, orders in another, parts in a third. That separation is what lets you search, sort and link without a tangle of repeated headings.
Relationships link tables, such as orders to the client who placed them. They let a form show client details beside an order without retyping the address. They also warn you when a linked record would be orphaned. Small offices often skip this step, then spend months fixing duplicates.
Set the link before you enter a large backlog. It is far easier to join an order to a known client at the start than to untangle three versions of the same name later. If a record would leave an order pointing nowhere, Base should stop you — that warning is a feature, not an obstacle.
The filed pile
Daily entry
A Base form presents fields in a readable order with labels that match office language. It can show related records side by side, so you enter an order against a known client. You can limit choices with list boxes instead of free text. The result is fewer typos and a cleaner table behind the form. Order the fields the way a conversation flows, not the way the table happens to store them.
Asking questions
A query filters and sorts records according to rules you set. You can list clients with no recent order, or parts below a stock level. Queries can also combine fields from linked tables for a report. Run a query on a copy first when the data is live. Name the query for the question it answers, so the next person knows why it exists.
Readable output
A report arranges query results for printing or PDF export. It suits an invoice list, a stock warning, or a client summary. Keep the report separate from the table so the data stays editable. Preview the report before you rely on it in a meeting.
Base can also use a spreadsheet or a text file as a data source in simple cases. Writer mail merge can draw on Base records for letters and labels. That link is useful when a list lives in Base but the output is a document. Test the link with one record before a full run.
Base help sits inside the suite help. Like Writer and Calc, Base has its own area in the online help system. The help explains forms, queries, and data sources as part of the suite. Press F1 for built-in help when it is installed. Search using the exact dialog name you see on screen.
Read the help and extensions guideBase is not a multi-user server database for a large organisation. It does not replace backups, access control, or a proper audit trail. When many people edit at once or records grow large, a dedicated database system fits better. Recognising that limit early saves a painful migration later.
A Base file holds personal or business data, so it needs the same care as any office file. Store it in a backed-up folder and limit who can edit it. Export a copy before you change table structure. A small database with a backup is safer than a large one without.
Do not try to model the whole office in a weekend. Pick one record type, build its table, and create a form for daily entry. Add a second table only when a real link appears. That small start teaches you where Base helps and where it does not.
Keep the model close to office language. Name tables and fields as your team names them in speech. A field called Client Email will be understood faster than a coded abbreviation. Document the purpose of each table in a short note. Future you will thank present you when a query needs a change.
Questions
Use Base when records need relationships, forms, or repeatable queries. Use Calc when the task is mainly calculation, sorting, or a short list without linked tables.
No. Base is a front end inside LibreOffice for forms, queries, and tables. It is suited to simple office data tasks, not large multi-user server work.
Still unsure which tool fits the list on your desk? Leave your email and we will point you to the right guide.
Break LibreOffice Guides, 42 Grafton Street, Dublin 2, Ireland. Phone +353 1 611 5607. Email info@break.ie. Monday to Friday, 9:00 AM to 6:00 PM.
If your records arrive as a spreadsheet, start in Calc and move to Base only when the links between lists start to matter. That keeps the work in the tool that fits it.
Contact Break LibreOffice Guides
