Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
The file (fetching and) processing takes place on a Solaris box; I'm not aware of any way of running VB script without using a Windows OS.

As a total aside, I am beginning to dislike this problem, as it looks like I'm going to have to use SOAP to fetch the file now (and in some awful flat WSDL format) which is causing completely different problems - but I am betting that other clients will wish to supply (non binary-xml) Excel, so the current parsing solutuion is of use. Look out for my next question in SoPW!


In reply to Re^3: Problems with Microsft's new Office 'XML' by graq
in thread Problems with Microsft's new Office 'XML' by graq

Title:
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 How to display code and escape characters are good places to start.