Issue 365 - TTEST produces error 508, bug in check for allowed values?
Summary: TTEST produces error 508, bug in check for allowed values?
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: 614
Hardware: PC Windows 95
: P3 Trivial (vote)
Target Milestone: ---
Assignee: issues@www
QA Contact: issues@www
URL:
Keywords:
: 381 406 686 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-02-02 12:51 UTC by issues@www
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2001-02-02 12:51:03 UTC 
The TTEST function seems to think my input in not correct, if I type
=ttest(e4:e6;e9:e11,2,1) or similar functions (where e4:e6 and e9:e11
contain random numbers, it returns a Err:508.
When I make exactly the same spreadsheat in Excel, I can load it into
Openoffice, and it gives me the correct answer, and the same formula is
in the cell. However, when I click with my mouse on that cell (in order to type
something there) and press excape again, it seems to recalculate the formula and
gives the Err:508 as result (thus without modifying the data!!).
Saving this (changed) document again to excel leads to a =#N/A in the excel file.

I think the spreadsheet seems to determine that I mistyped my formula, but
I do not think I did, because it is exactly the same as when loaded from an
excel file.
Comment 1 oc 2001-02-02 15:07:50 UTC 
Known problem, should be fixed in next version
Comment 2 issues@www 2001-02-02 16:25:29 UTC 
occurs only under win95/98/ME (not NT/00), in fact almost no formula works..
fixed in util/tools/source/intntl/intnwnt.cxx r1.2 which will be included in 
OO619B
Comment 3 issues@www 2001-02-02 18:11:56 UTC 
.
Comment 4 niklas.nebel 2001-02-07 09:11:19 UTC 
*** Issue 381 has been marked as a duplicate of this issue. ***
Comment 5 stefan.baltzer 2001-02-23 13:07:01 UTC 
*** Issue 406 has been marked as a duplicate of this issue. ***
Comment 6 oc 2001-02-26 13:35:18 UTC 
Fix verified in OO619
Comment 7 oc 2001-04-12 08:00:53 UTC 
*** Issue 686 has been marked as a duplicate of this issue. ***