Earlier, you commented:
*chuckling*..well, I feel my old friend 'Feature Creep' rapidly approaching.
Isn't it the man from the government that says: "I'm here to help." Much
to everyone's cynical disbelief, of course. But, that's what I want to do.
OK, I did put that part in the beginning that says it was for someone with no database
experience at all - so I should have a glossary.
I get the impression that you really know what you're talking about. But
the 'trick' (in my view) is being able to carry others along with you in your
explanation. I *have* had database experience. But it was so old as to
be counter-productive, rather than helpful. I need[ed] to be babied along.
As for spelling and consitency in terminology...guilty as charged.
No charges and no guilt. I just have a knack for proof-reading.
(But not necessarily my own expositions - that's genius level)
As for relational vs Flat and the word 'native'. In my mind if one is precise there is no such thing
as a flat Base databae, nor a hierarchical one. Ther is only one 'native' Base database
type and that is relational. You can create a Base file that connects to a flat database file,
but the database is the flat file not the Base file. Maybe I should not use the word 'native',
perhaps 'default' would be better. I could sidestep the whole issue but looking at how it
is worded on the Base information page at the OpenOffice site "BASEs own built-in HSQL
database engine.", and given the fact that if you create a new Base document with all default
settings (File>New>Database Finished [name the file] ) you have a relational database, the term
native database engine seemed appropriate.
I'm not quibbling with the term. Any term. Or terms. It's aiding
in comprehension that's driving me, and, I suspect, you. If there's
an element of uncertainty about how someone will 'read' and
comprehend a particular _expression_, expand on it at the first
point of use, or refer back to the definitions/glossary.
I still have no idea what those SQL acronyms actually mean and
what their relevance is. Nor what the equivalents are for field, record,
etc. Or is it simply a matter that I don't need to know?
Anyhow, I have made quite a few changes to the file over the weekend and hopefully you will find
this next cut a bit easier to follow. Thanks for the input.
You'll need to remind me where I found version 1 and where
I'll find your revised version. Not only do I want to help, I also
want to make use of the Base program! My geriatric MS-DOS
pop-up database can't go on forever!
Perry
New Zealand
