Kexi/Handbook/Building Simple Databases/Designing Forms/Forms versus tables: Difference between revisions
m (grammatical changes for readability) |
m (grammatical changes for readability) |
||
| Line 5: | Line 5: | ||
<!--T:2--> | <!--T:2--> | ||
In chapter [[Special:MyLanguage/Kexi/Handbook/Building Simple Databases/Entering Data Into Tables|Entering Data Into Tables]] you learned about how to enter data directly into tables using their data sheet view. However, in many cases forms are better suited for the editing of existing data as well as the entry of new data: | In chapter [[Special:MyLanguage/Kexi/Handbook/Building Simple Databases/Entering Data Into Tables|Entering Data Into Tables]] you learned about how to enter data directly into tables using their data sheet view. However, in many cases forms are better suited for the editing of existing data as well as for the entry of new data: | ||
<!--T:3--> | <!--T:3--> | ||
* | * Like a spreadsheet a table can contain too many columns to display them within the width of the screen without scrolling. A form can display such data using fields (or field widgets) placed logically over a whole page. | ||
* A form displays the fields for one record at a time. This is less confusing than viewing data presented in the multiple row (record) format of a table | * A form displays the fields for one record at a time. This is less confusing than viewing data presented in the multiple row (record) format of a table | ||
<!--T:4--> | <!--T:4--> | ||
* A form allows you to | * A form allows you to arrange data fields into logical groups, thus increasing readability. Labels with additional information can be inserted to give users more hints on how to use the form or what given data fields mean. | ||
<!--T:5--> | <!--T:5--> | ||
* Command buttons can be used within forms for commonly used commands | * Command buttons can be used within forms for commonly used commands. A user can then use the form as if it were a standalone application without recourse to the Menu system. | ||
Latest revision as of 16:46, 16 June 2015
Forms versus tables
In chapter Entering Data Into Tables you learned about how to enter data directly into tables using their data sheet view. However, in many cases forms are better suited for the editing of existing data as well as for the entry of new data:
- Like a spreadsheet a table can contain too many columns to display them within the width of the screen without scrolling. A form can display such data using fields (or field widgets) placed logically over a whole page.
- A form displays the fields for one record at a time. This is less confusing than viewing data presented in the multiple row (record) format of a table
- A form allows you to arrange data fields into logical groups, thus increasing readability. Labels with additional information can be inserted to give users more hints on how to use the form or what given data fields mean.
- Command buttons can be used within forms for commonly used commands. A user can then use the form as if it were a standalone application without recourse to the Menu system.