Jean Hollis Weber wrote:
Dan Lewis wrote:
> On Thursday 24 February 2005 06:42, Iain Roberts wrote: > The title is Introduction to Data Sources and, to me, that means > accessing external sources in OOo (e.g Writer, Calc) for things > like Bibliography,mail merge, etc. > > At the moment the document seems to be a good introduction to OOo > Base, covering creating a database, tables, forms etc.; but doesn't > have anything about using those data sources in other components, > except that you hit F4 to do it. > > All this ambiguity in OOo means that I'm trying to review your doc. > without really understanding what it's trying to achieve. If it is > about using Base, I think it might be clearer if the title was > changed. If it is about data sources as I understand them, maybe > there should be more on how to access data sources in Writer and > Calc and less on forms, queries and reports in Base (though your > guide to creating a form looks really good - if only the Form > wizard was working for me on Linux - so should at least find its > way into another Base guide, if not this one).
It was my understanding that what I wrote should go into the "Getting Started" part of the OOo User Guide.
Yes, that was my intention for Dan's chapter. Therefore IMO the chapter should cover accessing other data sources as well as whatever needs to be said about getting started with Base -- or else we need two chapters: one on Base, and one on accessing other data sources. I haven't looked at the draft chapter yet, so I don't have an opinion about what's actually in it or how I would recommend proceeding.
What do others think about having two chapters? Would this be a logical division? Would it help with the terminology problem as well ("data sources" vs "database")?
The purpose for Introduction to Data Sources is to explain what to do to a person who has little if any knowledge of what a database is or how to make one. That is why there are so many screen shots. It seems to me that the database guide, itself, would not need this much detail. In it, the instructions should be on a higher level since the reader would know how to make a database with its tables, queries, forms, and reports. I doubt that what I have written would be very useful to these people.
I think it would be a good idea to have some getting-started type info in the first chapter of the Database Guide too. Many people will pick up only the Database Guide, but will need the introductory how-to-make-a-db info. From Garry's note it sounds like the database guide will also have that intro info, which is good.
Jean
I should be able to upload my review tonight. It will definitely be work in progress, but I'm happier that I understand what I'm reviewing now.
Iain.
