Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 469619

Summary: The cell displays as "#NAME?" in Open Office Calc
Product: Red Hat Enterprise Linux 4 Reporter: koka xiong <kxiong>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED DUPLICATE QA Contact: desktop-bugs <desktop-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 4.9   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-11-03 08:50:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description koka xiong 2008-11-03 07:24:51 UTC 
Description of problem:
The cell displays as "#NAME?" in Open Office Calc 

Version-Release number of selected component (if applicable):
every version,from 1.1.5-10-- to 2.4.1-17.6.fc9.x86_64

How reproducible:
always

Steps to Reproduce:
1.Start Open Office calc
2.Select one cell such as A1 then click function wizard f(x）
3.In the function wizard dialog,in the fomula chart =sum then click "OK" button
  
Actual results:
The A1 cell displays as "#NAME?"

Expected results:
The A1 cell should display null or sum or something instead of "#NAME?"

Additional info:
Comment 1 Caolan McNamara 2008-11-03 08:50:29 UTC 
Not really, "#NAME" is for an invalid equation, so if "=sum" is the equation then null or something else would both be wrong. This is really the same as rhbz#469630 in that you want the function wizard to only allow a valid equation to be entered.

*** This bug has been marked as a duplicate of bug 469630 ***