Microsoft Office Forums

Go Back   Microsoft Office Forums > >

Reply
 
Thread Tools Display Modes
  #1  
Old 01-29-2015, 12:38 PM
Boyko Boyko is offline It looks like a bug in Lookup command Windows 7 64bit It looks like a bug in Lookup command Office 2010 64bit
Novice
It looks like a bug in Lookup command
 
Join Date: Jan 2015
Posts: 8
Boyko is on a distinguished road
Exclamation It looks like a bug in Lookup command

Please look at the Tables 1.X and Tables 2.X in the attachment.

The formulas in Tables X.1 are absolutely identical and created via copy & past by formula&format. The surprise is that the LOOKUP command in Table 1.1 cannot locate the correct (sR/s0) coordinate from Table 1.0 in the first column of the table while in any other columns in Table 1.1 or Table 2.1 the same command is OK.

Does someone know what is the reason for LOOKUP to behave differently in these two examples. I did various of test and I did not find the reason.



Thank you very much in advance
Attached Files
File Type: xlsm Test LOOKUP.xlsm (30.8 KB, 10 views)
Reply With Quote
  #2  
Old 01-29-2015, 01:03 PM
Pecoflyer's Avatar
Pecoflyer Pecoflyer is offline It looks like a bug in Lookup command Windows 7 64bit It looks like a bug in Lookup command Office 2010 64bit
Expert
 
Join Date: Nov 2011
Location: Brussels Belgium
Posts: 2,779
Pecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant future
Default

The search vector for LOOKUP needs to be sorted ascending.
Try =INDEX($B$5:$B$13;MATCH(K6;C5:C13;0)) instead
Why it works in the second table I don't have time to search for now. Will get at it later
__________________
Did you know you can thank someone who helped you? Click on the tiny scale in the right upper hand corner of your helper's post
Reply With Quote
  #3  
Old 01-29-2015, 03:43 PM
Boyko Boyko is offline It looks like a bug in Lookup command Windows 7 64bit It looks like a bug in Lookup command Office 2010 64bit
Novice
It looks like a bug in Lookup command
 
Join Date: Jan 2015
Posts: 8
Boyko is on a distinguished road
Default

I also did it using INDEX and MATCH however, my question was why LOOKUP works fine with Table 2.x but does not work with Table 1.x
The trends of the data in both tables are the same.
Reply With Quote
  #4  
Old 01-29-2015, 03:44 PM
Boyko Boyko is offline It looks like a bug in Lookup command Windows 7 64bit It looks like a bug in Lookup command Office 2010 64bit
Novice
It looks like a bug in Lookup command
 
Join Date: Jan 2015
Posts: 8
Boyko is on a distinguished road
Default

Please not that MATCH work with option 0 for Table 1.x It does not work with option 1. However MATCH with option 1 works for Table 2.x regardless that the data are not sorted. Something similar happened with LOOKUP.
Reply With Quote
  #5  
Old 01-30-2015, 03:46 AM
Pecoflyer's Avatar
Pecoflyer Pecoflyer is offline It looks like a bug in Lookup command Windows 7 64bit It looks like a bug in Lookup command Office 2010 64bit
Expert
 
Join Date: Nov 2011
Location: Brussels Belgium
Posts: 2,779
Pecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant futurePecoflyer has a brilliant future
Default

1.The LOOKUP vector ( in your case col C) must be placed in ascending order otherwise the results might be wrong ( see https://support.microsoft.com/kb/324986)
2. The MATCH function works perfectly with option 0 (see attached)
Attached Files
File Type: xlsm Test LOOKUP.xlsm (30.1 KB, 9 views)
__________________
Did you know you can thank someone who helped you? Click on the tiny scale in the right upper hand corner of your helper's post
Reply With Quote
  #6  
Old 01-30-2015, 09:36 AM
Boyko Boyko is offline It looks like a bug in Lookup command Windows 7 64bit It looks like a bug in Lookup command Office 2010 64bit
Novice
It looks like a bug in Lookup command
 
Join Date: Jan 2015
Posts: 8
Boyko is on a distinguished road
Exclamation

Quote:
Originally Posted by Pecoflyer View Post
1.The LOOKUP vector ( in your case col C) must be placed in ascending order otherwise the results might be wrong ( see https://support.microsoft.com/kb/324986)
2. The MATCH function works perfectly with option 0 (see attached)
Again, I would like to stress again my question: Why LOOKUP works for Tables 2.x but it does not work for Tables 1.x. In both tables the values in Column C are not in ascending order. The trend in the values is the same in both tables: increasing until certain value and then decreasing.
Reply With Quote
Reply

Tags
bug, lookup



Similar Threads
Thread Thread Starter Forum Replies Last Post
Lookup angie.chang Excel 1 07-27-2012 09:45 PM
It looks like a bug in Lookup command Possible Lookup Karen222 Excel 3 01-10-2012 05:41 AM
It looks like a bug in Lookup command LookUp aztiguen24 Excel 5 05-24-2011 03:57 AM
It looks like a bug in Lookup command Using the LOOKUP Command Grapejuice Excel 2 10-15-2008 02:02 PM
Add-In:How to add command right click command bar phang Outlook 0 01-15-2007 02:53 AM

Other Forums: Access Forums

All times are GMT -7. The time now is 11:10 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
Search Engine Optimisation provided by DragonByte SEO (Lite) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
MSOfficeForums.com is not affiliated with Microsoft