
Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
Thanks!
Mind if I ask a semi-related question?
Is there an "authoritative" tome (preferably short :-) that talks about
the ins and outs of database design? Pitfalls and pratfalls the should be
avoided? Etc etc etc.
and an unrelated question (about this news group). In general is this a
"top posting", "bottom posting" or "what ever floats your boat" group?
I've seen examples of both in the group, without a lot of subsequent
flaming for 1 or the other so I assume "what ever" is the norm, but want
to make sure before I piss people off. (this is top posted because that's
what you did, in case I'm wrong :-)
Bruce
> If one trip can involve many people, it seems you will need 3 tables: -
> Employee: one record for each person, with an EmployeeID primary key. -
[quoted text clipped - 8 lines]
> at:
> http://allenbrowne.com/casu-23.html

Signature
+-------------------+---------------------------------------------------+
Bruce Bowler | Lose an hour in the morning and you will be all day
1.207.633.9600 | hunting for it. - Richard Whately
bbowler@bigelow.org |
+-------------------+---------------------------------------------------+
Evan Keel - 03 Apr 2008 20:11 GMT
I haven't found a short, authoritative tome. But if you understand
normalization at least to 3rd normal form you will have a pretty good
design. The rules are simple:
1. No repeating items. This means no columns like Month1, Month2, Month3,
etc. And each column represents one concept. So no column data like
1,"Wilson", "Michigan"
2. In the case where a table has a composite key, all non-key columns must
be dependent on the full key
3. No non-key dependencies
If you get this far you will eliminate insert, update, and delete anomalies.
Google "Normalization"
Evan
> Thanks!
>
[quoted text clipped - 25 lines]
> > at:
> > http://allenbrowne.com/casu-23.html
John W. Vinson - 03 Apr 2008 22:04 GMT
>Is there an "authoritative" tome (preferably short :-) that talks about
>the ins and outs of database design? Pitfalls and pratfalls the should be
>avoided? Etc etc etc.
"God must love standards, She made so many of them..." <g>
Here are some links to tutorials and resources. Note that they don't all agree
with one another on all details.
Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html
The Access Web resources page:
http://www.mvps.org/access/resources/index.html
A free tutorial written by Crystal (MS Access MVP):
http://allenbrowne.com/casu-22.html
MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
>and an unrelated question (about this news group). In general is this a
>"top posting", "bottom posting" or "what ever floats your boat" group?
>I've seen examples of both in the group, without a lot of subsequent
>flaming for 1 or the other so I assume "what ever" is the norm, but want
>to make sure before I piss people off. (this is top posted because that's
>what you did, in case I'm wrong :-)
There's not a strong group culture on the subject, and some regulars top post;
some bottom post; and some (like me) Do It Right, trimming and interposting.

Signature
John W. Vinson [MVP]
Armen Stein - 08 Apr 2008 04:24 GMT
>Is there an "authoritative" tome (preferably short :-) that talks about
>the ins and outs of database design? Pitfalls and pratfalls the should be
>avoided? Etc etc etc.
I like Database Design for Mere Mortals by Michael Hernandez. I don't
agree with everything (for example I name all my tables in the
singular, not the plural), but it's a great explanation to start out.
It's easy to read, too - not like the insomnia cure many database
design books offer.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com