[thelist] DB Design question

[Jeff Howden]

joshua,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Joshua Olson
>
> > Question: Assuming there will be a master of list of
> > hundreds of ptotential breeds (all inactive at the
> > start) from which the admin will make a few score
> > active for regular use, what's a good way of designing
> > the (Access) database holding this information.
> >
> > 1. Adding an active/inactive column to the existing
> >    AnimalBreeds table?
>
> This will depend on how many shelters the single
> database manages.  If it's one, then you are ok with
> putting the active/inactive column in the AnimalBreeds
> table.
>
> I'd recommend you avoid option 2 altogether.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

i'd like to second that, bob.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> A middle of the road option (and one that will allow for
> multiple shelters) is to put just the active/inactive
> flag in a separate table.
>
> IE, the table may contain 2 columns
>
> BreedID, IsActive
>
> If you have multiple shelters, add ShelterID to that
> table.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

or, assume if the record exists in this joining table that the breed is
active, otherwise it's inactive, in which case you can drop the isactive
column entirely.

.jeff

——————————————————————————————————————————————————————
Jeff Howden - Web Application Specialist
Résumé - http://jeffhowden.com/about/resume/
Code Library - http://evolt.jeffhowden.com/jeff/code/