Combo box returning wrong results in Access 2010

[andigirlsc]

I have an unbound combo box that I set up in a form using the combo box wizard
in Access 2010. I selected the option that says, “Find a record on my form based
on the value I selected in my combo box.” The problem is that the combo box will
not always display the correct record. It seems to only display the first record
of a group of similarly named records in a table. I have found similar posts,
but no solution.

Example:

  
Last Name  First Name  SSN
Smith      Alex        123-45-6789
Smith      Jane        234-56-7891
Smith      Mary        345-67-8910

If I select Smith Jane, the record for Smith Alex will display. I know that this has something to
do with the bound column property, but I am unsure what to do to fix the issue.

What I have tried:
I tried setting the primary key as the
first field, but then I could only search by the primary key, which is
unrealistic for this database. Users will be searching based on last name. How
do I make the combo box select whichever record I select from the drop down


list?

[ranman256]

As shown, the bound column should be 3.
Smith may show, but inside the combo , it = [ssn]

You could combine the columns 1 & 2 ( [last] & "," & [first] as Name ), because when you pick Jane smith, you will only SEE smith. (what value is that with 3 smiths?)
that way you see SMITH,JANE, and the bound col = 2

[andigirlsc]

SOLVED (for now)

I scrapped the combo box and started the wizard again. Then, I set the SSN as the first column, (which is the primary key) allowed it to be hidden and the combo seems to work fine. I thought it would force me to search by primary key if I did this, but it didn't.

[Missinglinq]

Everyone be aware that this is cross-posted at

http://www.dbforums.com/microsoft-ac...ss-2010-a.html

Please, if you are going to cross-post, mention that fact in your all of the identical posts. This helps to prevent the volunteers who give of their time from wasting that time by working at cross purposes; giving responses that have already been given elsewhere, even giving responses to a problem that has already been solved elsewhere.

Thanks.

Linq ;0)>

[andigirlsc]

Sorry. I only cross-posted (which I wasn't aware was an issue) because some forums get quicker responses than others. Also, some responses are more helpful than others. I never post when there is already a working solution available. I will mention that it is cross posted next time.