Krambambuli - I also agree, an rtf would be just fine in my case. I just want to make sure that this process spawns something that will open in Word by default. I'm sure my users can go through the Save As and change it to an actual Word file after they are all done with it. Unfortunately, the code referenced in that page is no longer available. :(

jethro - What I meant was that it would just dynamically generate html which was displayed on screen just like a regular web page. No file was bring created or anything, it just shot back the text I wanted as html. The formatting that I wanted (only referring to extra line breaks) was via html tags. There are no font changes, or anything else. The web page output is as expected. This was only a temporary measure as I knew what I wanted the end result to look like but didn't know how to generate the Save As prompt for the download, and I figured that getting to that point wouldn't require much difference in the code (hoping I'm correct on that!) Although, I do think I get your point. Instead of generating a doc/rtf file to be downloaded, I could just write to the server and provide a link on the html output screen, and the user could just right-click and Save Target As, or click and open it directly, correct? This will be hosted on a web server and all users will have access. (Note: I would actually much prefer to create some sort of souped-up Word document that does all of it internally, but I don't know how to program like that. I do have a good grasp on perl which is why I went this route instead.)

Marshall - I'm assuming you are referring to the same thing as above in writing the file to the web site and providing a link. I might go that route. Just out of curiosity, where would be a good place to go to learn about that Win 32 OLE thing? Just in case I do want to get fancy with it.

Thanks much, all!

In reply to Re^2: Help generating MS Word .doc file from perl by schick79
in thread Help generating MS Word .doc file from perl by schick79

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.