[AccessD] Normalizing issue

Same here. 
 
The number of records that have a second last name vs those that don't dosen't warrant our efforts to program around it. We put the burden of keying it in properly on the business/clerical departments.

Jim Dettman <jimdettman at earthlink.net> wrote:
Susan,

I make it part of the last name field.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
Sent: Thursday, June 23, 2005 10: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


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



May God bless you beyond your imagination!
Lonnie Johnson
ProDev, Professional Development of MS Access Databases
Visit me at ==> http://www.prodev.us





 





		
---------------------------------
Yahoo! Sports
 Rekindle the Rivalries. Sign up for Fantasy Football