summaryrefslogtreecommitdiffstats
path: root/kexi/doc/handbook/html.tmp/01_04_00_who_needs.html
diff options
context:
space:
mode:
Diffstat (limited to 'kexi/doc/handbook/html.tmp/01_04_00_who_needs.html')
-rw-r--r--kexi/doc/handbook/html.tmp/01_04_00_who_needs.html24
1 files changed, 24 insertions, 0 deletions
diff --git a/kexi/doc/handbook/html.tmp/01_04_00_who_needs.html b/kexi/doc/handbook/html.tmp/01_04_00_who_needs.html
new file mode 100644
index 00000000..33a5f379
--- /dev/null
+++ b/kexi/doc/handbook/html.tmp/01_04_00_who_needs.html
@@ -0,0 +1,24 @@
+<h2>1.4. Who needs databases?</h2>
+
+<p>
+Stick to spreadsheets if:
+</p>
+<p>
+</p><ul>
+<li>Your needs are limited and your data will never grow to large volumes (can you actually forecast that now?)</li>
+<li>You are unable to acquire the methodology of database construction.
+You may however consider either outsorcing this task to someone else or using simpler tools.</li>
+<li>You use complicated spreadsheets and you lack time or money to switch to databases.
+Think or ask someone whether this does not lead down a blind alley.
+Don't count on magical tools that would change your spreadsheet (regardless how well made) into a database.</li>
+</ul>
+
+<p>
+Consider using databases if:
+</p>
+<ul>
+<li>Your data collection expands every week.</li>
+<li>You often create new spreadsheets, copy within these and you feel that this work
+is getting more and more tedious. In this case the effort of switching to databases easily pays off.</li>
+<li>You create reports and statemets for which the table view of a spreadsheet is not suitable. You can then consider switch to using a database with form views.</li>
+</ul>