[AccessD] Normalization discussion

So the database is going to be relatively small so you probably don't need to
consider normalisation 

To my thinking it's pretty much as Rocky posted - practicality!

Avoid having null fields, use minimum, or maximum values as meaning no entry and
boolean (True/False) probably take 2, or 4 bytes where a simple string "Y" or
"N"  value is only 1 char and more understandable.
Avoid requiring any auto-sequencing to be strictly ascending
Create the main entry with a form, then allow that entry to be selected from the
database to create the associated detail 
Also consider timestamps if you need auditing or just ordering of the data
entries.

Just  keep the reporting options open to allow multiple entries of subsidiary
entries.
And - test the reporting as you go along with the design.

And don't forget the backup and recovery planning - 
How are you going to record what happens throughout the days data processing in
order to do a recovery from the previous evening's off-site backup. 

JimB


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, August 29, 2014 8:20 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Normalization discussion

<jamesbutton at blueyonder.co.uk> wrote:

> And I would include a searchable comments field on many of the entries so
> you
> can include a short set of notes - such as a "See documents in folder ___"
> Also consider that many of the 'acquired from' places will probably not
> exist,
> or have moved shortly after you get the animals from them - otherwise why
> would
> they not keep the animals
>

==========We're an educational nature center. Everything here is native to
Kentucky. Mostly, they're wildlife that can't be released to the wild and
they come via rehabbers and rescues. Many of those places are well
established, but you're right, they won't always be there, but that would
be true of any business.


>
>
> And - will you be getting offspring from them - that will lead into a
> whole new
> concept of hierarchical entries for descendents of descendents of ...
>

===========I'll be using a self-join for those.

>
> Think of the entries if you're breeding mice - or spiders!
>
> ===========No spiders or insects here, although we do have a few
collections (all dead fortunately). Few of the animals here are allowed to
procreate -- the elk, bison, deer, turkeys, and quail.

Susan H.
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com