Kexi/Handbook/Building Simple Databases/Designing Forms/Forms versus tables: Difference between revisions

From KDE UserBase Wiki
(add prevnext)
m (grammatical changes for readability)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
====Forms versus tables====
<languages />
<translate>


In chapter 5.2 you learned about how to enter data directly into tables using their data sheet view. However, in many cases forms are better suited for data entry:  
==== Forms versus tables ==== <!--T:1-->


* A table can contain too many columns to display them on your screen. A form can display such a data using multiple rows.  
<!--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 for the entry of new data:


* A form allows to visually split 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: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.  


* Command buttons can be used within forms for commonly used commands so users can use forms in a similar way as a standalone applications they know.
* 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


In data sheet view displaying multi-row data text fields or images is as easy as within forms.
<!--T:4-->
* 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-->
* 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.
<!--T:7-->
{{Prevnext2
{{Prevnext2
|prevpage=Special:MyLanguage/Kexi/Handbook/Building_Simple_Databases/Designing_Forms/Most_important_terms
|prevpage=Special:MyLanguage/Kexi/Handbook/Building_Simple_Databases/Designing_Forms/Most_important_terms
Line 19: Line 28:
}}
}}


<!--T:8-->
[[Category:Kexi]]
[[Category:Kexi]]
[[Category:Tutorials]]
[[Category:Tutorials]]
</translate>

Latest revision as of 16:46, 16 June 2015

Other languages:

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.


Retrieved from "https://userbase.kde.org/index.php?title=Kexi/Handbook/Building_Simple_Databases/Designing_Forms/Forms_versus_tables&oldid=348931"