From: tpocccfo on
I am having a problem with a vlookup fromula returning an #N/A value when
using a cell with another vlookup formula as the lookup_ value. I created
this same spreadsheet a year ago and it worked fine. I even opened the old
one and I can't see any differences at all. I'd appreciate any help anyone
can give.
--
tpocccfo
From: Fred Smith on
We'd be happy to help, but you need to meet us halfway.

What's the formula?
What data is providing the #N/A result?

Regards,
Fred

"tpocccfo" <tpocccfo(a)discussions.microsoft.com> wrote in message
news:6EFE978D-A5DE-4DCC-8B4F-2B4D692BF67D(a)microsoft.com...
>I am having a problem with a vlookup fromula returning an #N/A value when
> using a cell with another vlookup formula as the lookup_ value. I created
> this same spreadsheet a year ago and it worked fine. I even opened the old
> one and I can't see any differences at all. I'd appreciate any help anyone
> can give.
> --
> tpocccfo

From: L. Howard Kittle on
Well, if I understand correctly, what you describe should work and did on my
small test.

So the #N/A says you think the lookup looks the same but it is not.

You say it worked before so perhaps something has corrupted the lookup value
column entries, like some new imported data or someone changed something and
thought they got it back to original data...

Try a =A1=C1 type evaluation on the cells that return the n/a. If False
that is the villian.

HTH
Regards,
Howard


"tpocccfo" <tpocccfo(a)discussions.microsoft.com> wrote in message
news:6EFE978D-A5DE-4DCC-8B4F-2B4D692BF67D(a)microsoft.com...
>I am having a problem with a vlookup fromula returning an #N/A value when
> using a cell with another vlookup formula as the lookup_ value. I created
> this same spreadsheet a year ago and it worked fine. I even opened the old
> one and I can't see any differences at all. I'd appreciate any help anyone
> can give.
> --
> tpocccfo