Date: prev next · Thread: first prev next last
November 2018 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=121090

--- Comment #15 from Jean-Francois Nifenecker <jean-francois.nifenecker@laposte.net> ---
(In reply to Mike Kaganski from comment #14)
Well, if needed, the first sentence of the 4th param

Sorted is an optional parameter that indicates whether the first column in
the array is sorted in ascending order.

could be changed to something like:

Sorted(RangeLookup) is an optional parameter that indicates whether the first column in the 
array represents a range list sorted in ascending order.

This actually addresses the valid concern from comment 12.

In fact, IMO, the point is not exactly the description of this argument but the
description of its consequences on the function result when VLOOKUP() can't
match an exact value.

If set to 1/True

No exact match -> the result is an approximative match. The user has no clue
about that and could think the result is the actual match (most do!).

If set to 0/False

No exact match -> the result is a #N/A error. Now, the user actually *knows*
the looked up value was not retrieved and can take appropriate action.

Not sure if theses consequences are always made clear. During trainings I
always have to insist on this point because of the consequences of not
selecting the right option.

My 2 euro-cents.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.