| Home |
| Search |
| Today's Posts |
|
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
VLOOKUP() Bug in VBA?
When I call Application.VLookup() with the col_index_num parameter = 1 and
range_lookup=False, the function returns strange numeric values -- they look like something close to a row index for the matching value, but it's definitely NOT returning the matching string values in Column 1 of the data table range being searched. After the call IsError(retVal) is False, so the function thinks it has found an exact match. The exact same call with col_index_num set to some value 1 works fine and returns the expected data. Note also that using WorksheetFunction.VLookup() seems to make no difference. Is this a known bug? Does anyone know how to fix it? |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| If (Vlookup 0) working, but what if Vlookup cell does not exist | Excel Worksheet Functions | |||
| VLookUp - Does the VLookUp return the exact information? | Excel Worksheet Functions | |||
| Combine VLOOKUP and IF function so #NA isn't returned as a value from VLOOKUP | Excel Discussion (Misc queries) | |||
| Vlookup -=VLOOKUP(F9,LookUp1!$A$2:$B$1504,2,FALSE) | New Users to Excel | |||
| Vlookup info being used without vlookup table attached? | Excel Worksheet Functions | |||
Threaded Mode
