Adding alternative names that mean the same key

[Zetheroth]

I've got an issue where certain users of the document put the names differently no matter how I try and tell them it will change, is there any way to assign 2 names to equal one key?

[Minty]

If this is on an access form, use a combo box to restrict their available options.

[Zetheroth]

It is in a combo box, but they just added another name to the list, which causes the system to think that the same buyer is actually 2

[Welshgasman]

So is that via the NotInList event? or do they go to the buyer form and deliberately add the same buyer?

[Gicu]

The answer is yes, you can create new table to hold the association (AutoID_PK,ProperName, AlternateName) and link that in your queries (link AlternateName to Name in current table and apply criteria to ProperName).

Cheers,

[Zetheroth]

ya they were deliberately adding a buyer, but ive got my answer on how to fix it now, Thanks everyone

[Welshgasman]

Going to be a task assigning fake names to the real name,surely?
How do you work out what the real name is?

[Zetheroth]

its all stored down to a primary key number anyways, and the main name will be the one in the primary row, with a secondary and tertiary row for anyone who uses more than one name

[Welshgasman]

If that was me, I would probably start storing the user name of the creator of the record and then be having words.

[orange]

I agree with the solution offered by vlad. And, further to Paul's recording some names and having a talk, when people can add "junk/fake" values contrary to instructions, that is a management issue rather than a technical issue. Often corrected through some training or adjusting program logic/validation to prevent/restrain unwanted values.
We've all experienced some form of this, so it isn't new ground.

[Micron]

Isn't this a simple matter of setting Limit To List = Yes?

[orange]

Micron,
I think that's all that's required.

[Gicu]

Post # 3:

It is in a combo box, but they just added another name to the list,

Post #6:

ya they were deliberately adding a buyer

Sorry but I don't think so, the OP says the users are deliberately adding the name to the list (table), so it will be in the list and not restricted by the LimitToList.
Cheers,

[Micron]

You clean up the list and leave in the valid values. Then they can't add whatever they want after that. Or is that not what is wanted?
This is being done in a form, not a table? It was asked but not answered. Saying it's being done in a combo doesn't answer that when table lookup fields can present combos too.

It is in a combo box,

Besides, if OP has a solution as per post 6, why did I even bother to raise the question?

[Gicu]

I wouldn't know were the new entries are done but to me being done "deliberately" would signal that the users wouldn't stop once the list was "cleaned", they'd find a way to add them again.

And I believe the solution mention in post 6 was referring to the one I offered in post 5, but again, not a mind reader so only the OP would know for sure .

Cheers,