FM-Easybase
Create your individual database application without programming knowledge
Filemaker basic tool FM-Easybase
Practical implementation of the example project
1. Which tables are needed?
An example with multiple tables.
The saved tables are classified into three columns below:
Column 1: a layout is created in the menu for these tables, with which master data can be entered
2. Table structure
Column 2: here, the tables that are related to a table in column 1 are selected by mouse click
Column 3: in this column, tables can be specified that are related to a table in column 2.
Main table → Subtable → Sub-Subtable
This is referred to as 1:n
3. Define table contents
After these preparations, the field names are defined in a service layout for each of the specified tables.
In the following example for the tables Customers and Articles, you can also see in the green area the selection of the fields that are made available for sorting and display in the portals, bookings and reports.
Service layout for the tables Customers and Articles:
4. Layouts
There are 3 different layout types:
Type A: Layout for a single (main) table with create / edit / delete for all fields
Type B: Layout for a main table (6 selected fields are displayed) and a 2nd table dependent on this table (with create / edit / delete of all fields). In addition, another table dependent on the 2nd table with 6 fields can be managed in this layout
Type C: Layout for a main table with a display of up to 4 dependent sub-tables with 3 selected fields each
Type A
The empty spaces in the layout result from undefined field names.
In this example, the search mask is open. You can see that you can search by company name, postal code or industry. These fields were defined as search fields in the service layout (see above).
Type B
In this layout type, a sub-table is displayed for a main table
After selecting a branch, several contact persons can be entered here in the lower part (sub-sub-table). In the upper part, all fields are listed which were defined in the service layout for the table branches.
Type C
In this layout type, up to 4 portals with entries in associated sub-tables can be displayed for a data record from the main table.
5. Invoice and booking
In order to be able to create an invoice or a booking, a booking schema must first be created. This schema defines which tables are involved in the booking and which fields are necessary.
The example shows the booking schema for invoices
After clicking on the displayed invoice header, the desired articles can be added.
After creating a booking schema, the customer address can be selected. This creates the invoice header.
The invoice then looks like this:
6. Evaluations
Evaluations are defined very easily using this schema:
The schema contains 3 blocks:
- Selection criteria
- Grouping criteria
- Total fields (calculations are possible with a formula editor).
Exactly those fields that were specified in the service layouts can be selected.
With this information you get the following evaluation:
