lookup() function bug?

[vito]

lookup returns wrong value instead of error, see screenshot attached

lookup.png (4.97 KiB) Viewed 8248 times

[stascheit]

The behaviour is correct (and corresponds also to Excel).

See the description in the manual:

Note:
If LOOKUP does not find a value that exactly matches Crit, the next smaller value is automatically taken.
If no smaller value exists because Crit is smaller than the smallest value available, the function returns the #N/A error value.

An error value is returned, if you have an example like this (Crit is smaller than the smallest value available):

[Devonboy78]

Just a small point; If the command is typed in as shown in the example =LOOKUP(3;A1:A3;B1:B3) ,Planmaker will report an error in formula Invalid characters.
The formula should read =LOOKUP(3,A1;A3,B1:B3) in order to work (manual, page 682, Syntax LOOKUP(Crit, LookupVector, ResultVector)

[stascheit]

Sorry, my mistake. I used the European locale for list separators and cell range and not the US/UK locale.
But also vito does...