On 07/02/2012, Nino Novak <nn.l...@kflog.org> wrote: > > As a consequence: It would help most, if the database set up barrier could > be > lowered. > > We therefore should ask (and try to learn) what makes database creation so > difficult, and how could we contribute to ease the learing curve? > > Or directly: how can we make database creation easy and a low-threshold > task? >
The statement made by someone that databases requires planned design _first_ is important to remember. But for a novice how do you make the plan? This is why the original poster was asked the question why did spreadsheet names have to be changed, although he doesn't think it important. It is important to know the objective. For example, we could be asked how to manoeuvre a 10-tonne truck a distance of 50 metres, when if we knew the objective was to buy a drink from the shop across the road, we could advise it would be easier to walk! A silly analogy but hopefully understood. Maybe the way to promote the option of designing databases is to describe particular scenarios and show how particular tasks can be performed using either a database or a spreadsheet. Users would then see two tutorial scenarios to show the (dis)advantages. Hopefully someone can suggest such a scenario or two please? -- For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
