[AccessD] Normalizing issue

If it isn't a middle or maiden name, what is it?  This gets even more
tricky with non-English names where "last" names can get really
confusing.  I generally provide a field for first, middle, and last name
and make it the responsibility of the user to enter the appropriate
value in the appropriate field.  The rules for parsing this can become
so draconian, that it hardly seems worth the work to do anything else.

Charlotte Foust


-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
Sent: Thursday, June 23, 2005 7:00 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Normalizing issue


How do you guys deal with people that use three or more names
professionally? I do -- Susan Sales Harkins. 
 
Do you store the second name with the first or use three fields? The
middle name really isn't a "middle" name. It's actually part of the last
name, but the last name is the real last name -- so if you stored it
with the last name, you'd have to depend on users to enter it correctly,
as in Harkins, Sales --  which is a mistake before you even get
started... And how do you write in the flexibility that handles 2 or 3
names? 
 
Susan H. 
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com