One simple-minded, OTTOMH approach (unless MS Word's formatting is somehow important):

  1. in Word 2010, edit in an end_of_record marker of any flavor you like, so long as it won't appear in the test.
  2. save the whole (edited) .doc as .txt
  3. read the .txt
  4. split on EOR to create an array (named for page number) per page of words.
  5. split each array's contents on spaces to a second-level array (named for the page number from which the first array was extracted) of individual words
  6. index to your heart's content...

Of course, this may not be the most efficient approach, but it certainly avoids "climbing that (Word object model) curve.


If you didn't program your executable by toggling in binary, it wasn't really programming!

In reply to Re: Win32 OLE Word Get Page Text by ww
in thread Win32 OLE Word Get Page Text by cormanaz

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.