Harlan Grove 2005-01-05 18:45:25 UTC ```The following formulas can be entered normally (i.e., not as array formulas) in Excel but must be entered as array formulas in Gnumeric in order to return the same results. =trend({1;2;3;4},{1;2;3;4},5) =growth({1;2;3;4},{1;2;3;4},5) Furthermore, given the following entries in A1:B6, 1 1 2 4 3 9 4 16 5 25 6 36 and 3.5 in A8, the following formula returns #N/A entered normally or as an array formula in Gnumeric but returns 12.5 in Excel. =trend(offset(B1,match(A8,A1:A6)-1,0,2,1),offset(A1,match(A8,A1:A6)-1,0,2,1),A8)``` Morten Welinder 2005-01-05 19:26:28 UTC ```Mostly a dupe of bug 162923. Keeping for the extra info. ``` Harlan Grove 2005-01-06 17:57:50 UTC ```The first section may not be a bug, just different functionality than Excel. As for the last formula, TREND isn't the issue. The term match(A8,A1:A6) returns #N/A, which is a bug *if* Gnumeric's MATCH function should default its 3rd argument to TRUE or 1 (like Excel), in which case match(3.5,{1;2;3;4;5;6}) should return 3, the greatest value in its sorted-in-ascending-order 2nd argument less than or equal to its 1st argument.``` Jody Goldberg 2005-01-10 01:50:56 UTC ```162923 is fixed (array results in expressions not entered as array formulas) and I just patched the type arg to default to 1 for MATCH. Thanks for noticing, we had several tests for match, but apparently missed this. patches will be in 1.4.2 ```