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


Jean-Francois,

+1
Thanks for this idea, below. I'd never thought of naming an array, and you are right, it would seem to make both generating AND understanding formulae easier. Plus there's less room for error. In my case I frequently use the same array for a variety of vlookups, so the added step of naming could end up saving me some time as well.

Carl


On 2/15/14 2:55 AM, Jean-Francois Nifenecker wrote:
Le 14/02/2014 23:06, Carl Paulsen a écrit :
A few hints for vlookups:  I find I usually want to add "hard"
references for the array so that it always looks at the intended rows of
the array.  To do that, you need to add $ before each cell reference in
the array.  So if the array of the function is A1:C100, I enter it as
$A$1:$C$100.  This forces vlookup to always look at those cells
regardless of what row the calculation is happening on.
Another way of achieving that is to name the array. This has my
preference because a named array makes formulae easier to understand.



--

Carl Paulsen

Dover, NH 03820


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.