[AccessD] Design question

Hi Richard

I can't get excited over tables of titles.  What's the point in having one?
Little if any savings or gains in space, performance, complexity,
ergonomics, etc - in fact the opposite, mostly.  Just let them type it in!
And store it in the record with the name(s).

Looking in my address book, I can see a Frau, a Mme and a Reverend Canon
amongst others.  And my own title, which I rarely use, almost never appears.
Who cares?!

Admittedly there is a narrower choice in the US, but here in the UK (just 30
miles from you, in Cheshire) + Europe the list could get quite long.

This is the voice of experience speaking - programming since before you were
born!

(just plain) John Robinson



> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Griffiths, Richard
> Sent: 10 December 2004 11:14
> To: AccessD at databaseadvisors.com
> Subject: [AccessD] Design question
> 
> Hi Group
> Design issue - how to store the title for a person record
> 
> Option 1
> 
> tblPerson
> -------------
> titleID
> firstname
> lastname
> 
> 
> Option 2
> 
> tblPerson
> -------------
> title (contains actual value from tblTitle e.g Mr,Miss, Mrs, Ms.,Dr.,
> Prof.)
> firstname
> lastname
>  
> 
> Issues
> 
> For option 1 - every time we need person details will require 
> a join on the table (makes sql verbose etc) - 
> 
> For option 2 - how to handle tblTitle changes - could use 
> ref. integrity or even simpler.....only allow user to add new 
> titles and not amend (can't see any reason to amend
> 
> anyway - amend 'Mr' to what??)
> 
> Anyone care to comment (can't believe I've 20 years 
> programming exp. and am asking this type of question - must 
> be my age (just hit 40 ))
> 
> Thanks
> Richard Griffiths