Off topic I know but I found this interesting - Microsoft introducing yet another bug into an existing product - so I did a bit more digging and found a few interesting options that may help. Somewhere, I saw it suggested that the xml file format has an extra element that makes it possible to say 'treat the cell contents as text even though it contains a number'. If I find that same page again, I will post a link to it. Furthermore, one of the responders to the list suggested that adding a trailing whitespace to the numeric value before inserting it into the cell may cure the problem. Cannot say if it works or not as I have not tested it yet.
Finally, the leading apostrophe works in earlier versions of Excel. Then the application - Excel that it - simply assumed - if a numeric value was entered into a text cell - that it should format the value in a specific way. The leading apostrophe simply over-rode this behaviour. --- On Mon, 10/27/08, Knudsen, Joe <[EMAIL PROTECTED]> wrote: From: Knudsen, Joe <[EMAIL PROTECTED]> Subject: RE: green corner in a cell warning about a number formatted as text To: "POI Users List" <[email protected]> Date: Monday, October 27, 2008, 1:39 PM Should I create a bug and upload the files? I think I would like to take a crack at doing the code any help would be appreciated. -----Original Message----- From: Nick Burch [mailto:[EMAIL PROTECTED] Sent: Monday, October 27, 2008 1:14 PM To: POI Users List Subject: RE: green corner in a cell warning about a number formatted as text On Wed, 22 Oct 2008, Knudsen, Joe wrote: > I created a simple one cell spreadsheet one with the warning and one > where I set the warning to ignore in Excel. Here is the diff after > running them through BiffViewer. Reading the BiffViewer out it looks > like it is not supported. Any ideas for next step to take, dig in and > add the feature? Any chance you could upload these two files to bugzilla? "recordid = 0x867" seems to be a FeatHdrRecord, which can have a few friends. I think some more support, and certainly some more tests will be needed in the low level poi, then something to tie it up with the usermodel. If you fancy coding that up, shout and we can give you tips, otherwise someone else tackling it'll find the two files handy :) Nick --------------------------------------------------------------------- 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]
