Holy Moly Drew, when did you add all that? I think that you added stuff
and then went back later while I was sleeping or something and added more!
I think that we should add some Macro related topics in a context where
they make sense; forms, for example. It is not clear that we even need a
place in the outline for this yet. If there is something that we want to
address and a simple macro is the solution, then add it.
andrew wrote:
Jean Hollis Weber wrote:
hmmm...I know that in an earlier email I said that I would help and
didn't care if I got any credit...OK, that was a bit over stated...I
guess I do kind of care after all.
I would never take anything away from Andrew, but the outline and
comments you mention where put up by me.
LOL - I know - Drew / Andrew - it can be a little confusing..anyway,
no harm, no foul as they say.
But Drew, I like taking credit for you work, especially all the groupies..
I've probably said this before, but one problem with a book such as
this is: how much to teach about relational databases themselves,
versus just explaining how to use the tools provided in OOo Base.
Obviously our main requirement is to cover OOo's tools, but I do like
the idea of including some instruction on database design as well.
Dan Lewis's "Getting Started with Base" chapter is great in that
respect.
How to strike a balance is a real trick, isn't it.
For example you mention covering the basics of relational database
theory - well, you can use Base to create a flat database just as
easily as a relational one, and in fact I would bet that the vast
majority of people falling into my fist category above will end up
doing just that.
I think that we MUST provide at least a minimal introduction. I have
seen numerous Base documents setup by new people that did not have a
clue. After I made some changes/recommendations, they understood the
difference. I would go so far as to create a simple example as Appendix
I and shift the other appendices down by one. That way, we can refer to
the appendix from time to time. Sure, it sounds a little bit like the
database design section in Appendix III, but that looks more like a
"look here for more information" appendix.
Then there is a real problem in that there are at least three distinct
user types.
First is the person that uses the database development part of it to
create a very simple database for personal use.
Second, the person using the database to development database
applications for others to use.
Finally, those that will be using those database applications created
by the second person.
Astute observation
At each of these steps more of the 'theory' of relational databases
can be introduced as needed. For real in depth discussion however I
would simply offer a list of references, this type of information has
been covered in great detail by others already. Not to mention that
Base can connect to a variety of DBMS engines and each will have
slightly unique features.
Although I like this approach, I think that we should discuss
duplicating information and using keys rather than duplicating the
information every time. If we mention "normal forms" apart from a casual
mention with a reference, we have probably made an error.
I think an odt file needs to be the baseline document
I agree.
--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
My Book: http://www.hentzenwerke.com/catalog/oome.htm
Info: http://www.pitonyak.org/oo.php
See Also: http://documentation.openoffice.org/HOW_TO/index.html
