OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-formula message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-formula] LOOKUP function


Hi,

On Thursday, 2008-03-06 17:30:40 +0100, Eike Rathke wrote:

> If the lookup matrix is a row vector or square or taller than wide, and
> the result vector is a column vector, then the value corresponding
> offset-wise is returned. Same if the lookup matrix is wider than tall
> and the result vector is a row vector.

I mixed up column vector and row vector terminology, of course that
should read:

If the lookup matrix is a column vector or square or taller than wide,
and the result vector is a row vector, then the value corresponding
offset-wise is returned. Same if the lookup matrix is wider than tall
and the result vector is a column vector.

> >   3) The lengths of the search vector and the result vector do not need 
> >     to be identical; however, when the match position falls outside 
> >     the length of the result vector, an error is raised if the result 
> >     vector is given as an array object.  If it's a cell range, it gets 
> >     automatically extended to the length of the searched vector.
> 
> But in the direction of the result vector, as I just found out.
> And: if just a single cell reference is passed, a column vector is
> generated.

Same here, a row vector is generated.

Sorry for confusion.

  Eike

-- 
Automatic string conversions considered dangerous. They are the GOTO statements
of spreadsheets.  --Robert Weir on the OpenDocument formula subcommittee's list.

PGP signature



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]