[AccessD] Design question

Too many dissimilar field requirements.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson
Sent: Wednesday, 10 July 2013 9:30 a.m.
To: Stephen
Subject: Re: [AccessD] Design question

Hi Stephen,

Is there a reason that Ewes and Sires can't be stored in the same table?

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stephen Bond
Sent: Wednesday, 10 July 2013 9:00 a.m.
To: Access Developers discussion and problem solving
Subject: [AccessD] Design question

Here's a design question I've never had to face before ... someone here
will
have for sure.

I am in continuous development of a system which logs and analyses milk
production from a sheep farm.  Recently the client has requested an
(another) upgrade, this one to store some genetic data as well.  So now
we
have 2 animal tables, tblEwes and tblSires.  

As part of the upgrade, a new Registration number is required for each
animal.  This must be unique across both tables.  How to implement?
Should I put in another table called, say, tblAnimalReg, with the
Registration number as PK?  And also store in this table the PK and
tablename of the animal it refers to.  Something strikes me as a bit
weak
about this ... but I can't put my finger on it.  Ideas please.

Stephen Bond


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

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