[AccessD] Design question

Actually, the Q was about Mr, Mrs, etc, not job titles.  Is Ms a
'miss'-spelling?

I suppose gender re-assignment would lead to a change ... but I'd avoid the
underwear allusion!

John


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Nicholson, Karen
> Sent: 10 December 2004 18:12
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Design question
> 
> 
> Letting the users type in anything that can lead to type'0s 
> is a recipe for data disaster.  Around here, titles change 
> like underwear, one day a person is an IS Support Specialist, 
> the next day he is an ITSO Support Specialist.  Keeping the 
> titles in a lookup table relieves so many headaches.  And 
> people can not spell.  So you have have sexretary, secratery, 
> etc.  Then, how are you going to run a report with a bunch of 
> titles that are misspelled?  Grumppp.
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Mark A Matte
> Sent: Friday, December 10, 2004 12:58 PM
> To: accessd at databaseadvisors.com
> Subject: RE: [AccessD] Design question
> 
> 
> Richard,
> 
> Earlier in this thread...the value of storing titles seperately was 
> questioned.  I recently did some work with a 'Process 
> Management' software 
> package.  There was an Org Chart built in (the titles were stored 
> seperately).  This allowed control of some processes that 
> were dependant on 
> title.  If titles were randomly typed in...you would have 
> some difficulty if 
> you wanted your app to do something for all 'managers' or 
> some other title.
> 
> Depending on the app...there can be some good reasons to 
> store the title
> 
> seperate...or some good reasons not to.
> 
> Just thought I'd add...
> 
> Thanks,
> 
> Mark A. Matte
> 
> >From: "Griffiths, Richard" <R.Griffiths at bury.gov.uk>
> >Reply-To: Access Developers discussion and problem
> >solving<accessd at databaseadvisors.com>
> >To: "Access Developers discussion and problem 
> >solving"<accessd at databaseadvisors.com>
> >Subject: RE: [AccessD] Design question
> >Date: Fri, 10 Dec 2004 17:10:56 -0000
> >
> >Thanks for your replies - I'll keep the table but simply 
> present this 
> >for use in a drop down combo and store the result in a text field. I 
> >appreciate the lookup of actual values entered - varying 
> typing skills 
> >could result in mistyped/spelled entries which then presents 
> the user 
> >with a duff list and the task of finding the duff entries - thanks. R
> >
> >-----Original Message-----
> >From: accessd-bounces at databaseadvisors.com
> >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan
> Harkins
> >Sent: 10 December 2004 16:44
> >To: 'Access Developers discussion and problem solving'
> >Subject: RE: [AccessD] Design question
> >
> >Good idea. :)
> >
> >Susan H.
> >
> >Using Susan's suggestion, I'd make it a tad bit different. When 
> >creating the combo box, for the Row Source use a SQL 
> statement using a
> >group-by to refer back to the same field that's being updated.  The
> user
> >can
> >still type in anything that is needed.  Do a requery on the On Enter 
> >event. This way all titles used are available and new ones can be 
> >added.
> >