Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

ParseExcel cannot open the original document (Excel 4.0). The specific error is "Couldn't open your file::Bad file descriptor."

As it turns out, I forgot that I was using ParseExcel::Simple. That wasn't really a problem, though, as when I switch back to ParseExcel, I see the same behavior.

Now, that was a great suggestion to look at the object using Data::Dumper. I did the following:

I dumped the objects as they were saved by OO, then did the same after saving (but not changing) the file with Excel. Two fields differed: _Value, and FmtIdx. It seems that the _Value field gets set to "GENERAL" for numeric fields by OO, and the value is in the Val field. Excel has the value in both places. In other words, you were correct to surmise:

that maybe the value you're looking for could be in:
print $oWkC->{Val};

I had switched over to ParseExcel::Simple because it was easier to use, but I suppose that if I'd like to get this vendor to send me usable files, I'll need to switch back and use the Val value. <sigh>


On further examination, that doesn't help the date formatting at all. I'll still have to convert that, but I'm not too worried about it. (It should be related to the Julian date.) Thanks very much for your help!

In reply to Re^2: Spreadsheet::ParseExcel incompatible with Openoffice? by pepik_knize
in thread Spreadsheet::ParseExcel incompatible with Openoffice? by pepik_knize

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (2)
As of 2022-05-18 04:24 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (68 votes). Check out past polls.