To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=53833
------- Additional comments from [EMAIL PROTECTED] Thu Sep 22 04:45:42 -0700 2005 ------- >>1. Why are numeric fields that are changed to text fields kept as numeric fields for calculations? >"1.) It's the same as for text cells converted to numbers. The first used cell format rules as long as the cell isn't Edited in the way that you've entered it by either doubleclicking it or using F2 and change something and close the cell. Entering new content to the cell will change it immediately. So, the true value of the cell is invisible to the user? >>Q. 2. If a numeric cell contains a formula using a reference to a non-numeric cell, why isn't an error message generated? >"2.) Because text cells have the value zero." The cells don't contain zero. They contain the value entered, and if that's anything but null it's something, numeric or not. (Note, I'm not talking about any invisible-to-the-user values, but what they can see.) [[Side note: I've just this week had to explain to my boss and a co-worker that the highlighting in an OOo text file when saved as a Word .doc can't be removed with the highlighting tool in Word since Word has 2 levels of highlighting and the highlighting tool in Word doesn't act on the same level OOo saved (OOo has 1 level of highlighting). ((Checked the DB here, and just like this report, the highlighting issue isn't technically a defect in OOo. In that case it's a defect in MSO...yet, it's still causing me problems in getting OOo adopted (see below). If a calculation doesn't match what Word says (or can't be proven to be more accurate as Gnumeric is), there's no way I can explain it to the boss.)) This has made me consider putting together a seperate 'OOo to MSO coverter' just so I don't have to get routinely embarrased even when does things correctly, though that would probably require me to create a macro for Word or Excel to clean up the differences, and nobody is going to install and run that macro so I'll have to do it before exchanging any documents. An 'insert MS quirks mode (incompatable)' for saving a file would be a good idea in these situations. ((A search of the DB here came up with no hits on this issue, though I might have used the wrong search paramaters.)) The usual comment after I explain the situation is 'Well, we just can't rely on that [OpenOffice.org] -- use MSO' or 'why do you insist on using OpenOffice?'. Beyond the embarasements, this is a big problem since I can't add OOo/OpenDocument to requirements documents on the contracts I'm on once people encounter a few of these these differences no matter if the implementation is technically correct or not.]] --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
