I'm trying to test if vlookup could behave in a way that I would not expect.

I have two tables, let's say table A holds unique individuals and their i.e.
social sec. numbers.

I have a table B, which lists individual coffee preferences. Generally, each
individual likes a unique coffee. However, a few like similar types. I.e. 2
individuals like mocha and 2 individuals like java, etc.

Basically, a one-to-many relationship exists between table A and table B.

If I use the SS# from table A, using vlookup, and map it to table B:

1) will vlookup always pull the first match from the table array?
2) it seems to me that option 1) is always the outcome - can that be not true?
3) if vlookup does not find a match, it usually gives me #N/A
4) can #N/A result using vlookup, in the example described above?

(my vlookups are always set to find the exact match)

Thanks

Hi!

1. Yes
2. Not using a basic lookup formula. You'd have to write a formula to
specifically look for the nth instance.
3. True
4. If your lookup_value is a SS# and ALL SS#'s are unique you should find a
match (if it exists).

Biff

"pepenacho" wrote in message
...
I'm trying to test if vlookup could behave in a way that I would not
expect.

I have two tables, let's say table A holds unique individuals and their
i.e.
social sec. numbers.

I have a table B, which lists individual coffee preferences. Generally,
each
individual likes a unique coffee. However, a few like similar types. I.e.
2
individuals like mocha and 2 individuals like java, etc.

Basically, a one-to-many relationship exists between table A and table B.

If I use the SS# from table A, using vlookup, and map it to table B:

1) will vlookup always pull the first match from the table array?
2) it seems to me that option 1) is always the outcome - can that be not
true?
3) if vlookup does not find a match, it usually gives me #N/A
4) can #N/A result using vlookup, in the example described above?

(my vlookups are always set to find the exact match)

Thanks