On Thu, 27 Jul 2006 15:00:02 -0700, InternRyan
<InternRyan[ at ]discussions.microsoft.com> wrote:
[Quoted Text] >I have set up a pretty simple db. One table with a list of people as a
>primary key (lastname,firstname) and then connected it to a table of expenses
>connected to those people, rental cars and hotel rooms mostly. I wanted to
>make the connection between the two the names which is why I made it one
>field instead of a last name field and a first name field. I created a search
>using a query that had [name] as criteria. I would like to be able to search
>for just powers instead of Powers,John and so I dont miss a Powers,John D
>entry accidentally. I wonder if this isn't a bigger problem than I think
>because *seperate issue* the way things are right now if someone isnt in the
>names database and you try to add an expense you have to stop and add them to
>the names database. I hope that made some sort of sense. Thanks for any help.
>
>Ryan
First off... Names ARE NOT UNIQUE. I know three Fred Browns, right
here in the little town of Parma; I once worked with Dr. Lawrence
David Wise, Ph.D. and his colleague, Dr. Lawrence David Wise, Ph.D.
You must have more information to uniquely identify an individual, and
your table should have a unique PersonID distinct from the name.
Secondly, it's almost universal to use two fields - first name and
last name. This lets you search for them individually; you can combine
them for display purposes.
If you use a Combo Box (say displaying the last and first names and
some other piece of information such as an address or phone number),
you don't have to worry about typing the name just right - you'll just
SEE the names that are already there. You can even use the NotInList
event of the combo box on a form to add a new name if you really do
have a new person to enter.
John W. Vinson[MVP]
|