[AccessD] Normalizing issue

The "nuisance" you cite is not much of a nuisance, IMO. Just create a Save
button or a Form_After_Update event that copies actual name to pen name in
the event of a blank pen name. Then the queries are simple.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: June 23, 2005 11:43 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [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.

========I'm in the middle of creating a database (pro bono) for a writer's
organization. It's a simple deal and will require little work -- but this is
already cropping up. These people will want their "writing" names with their
publications -- I'm thinking about just adding one more field to store their
"pen name" or whatever -- but then that becomes a nuisance if their name and
professional name are the same -- gotta fill in both or allow for the blanks
and go find the real name -- such a nuisance -- 

I think at this point the middle name is the best solution -- 

Susan H. 

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