D
duluth george
Data: running Word2007 on Windows XP fully up to date through Service Pack 3.
Inspiron 4150 with 512MRAM.
Problem: When using cntrl+F in "Find" mode, the program will go to 100%CPU
and enter into "program not responding" mode. Requires having Word enter
into document recovery and send error report sequence. And then have the
program reboot. Two additional details of the problem: 1) the problem only
exists on larger docx documents. Where I'm experiencing it is in a 360 page
report (~1M docx); and 2) it only happens when the search would require
wrapping from the bottom of the doc to restart the search at the top. It is
this last function that IMO is causing the problem: it doesn't execute the
"start at top" function. At this point it seems to send the program into an
endless loop.
Discussion: I have been having the above described problem with Word2007
since I purchased it several months ago. I have re-installed the program
once, thinking perhaps the problem was a disk error. No luck, the problem
re-occurred as soon as I tested it. Here is how I induce the problem:
As mentioned above, I'm editing a 360 page document. I will be mid-way down
the document and need to search for a text string. If the target text string
is below the search initiation point, the "Find" function works without
error. However, if the target text string is higher up in the document,
which would require the search function to re-initiate the search at the top
of the document, the CPU immediately goes to 100% and spins in perpetuity.
It requires forcing Word2007 to quit.
I have now adopted the routine of starting all text searches from the top of
the document and this has eliminated the program lockups. Oddly, the problem
seems to exist only on a large document. The search function on a small
document of only several pages seems to work without error.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...8&dg=microsoft.public.word.application.errors
Inspiron 4150 with 512MRAM.
Problem: When using cntrl+F in "Find" mode, the program will go to 100%CPU
and enter into "program not responding" mode. Requires having Word enter
into document recovery and send error report sequence. And then have the
program reboot. Two additional details of the problem: 1) the problem only
exists on larger docx documents. Where I'm experiencing it is in a 360 page
report (~1M docx); and 2) it only happens when the search would require
wrapping from the bottom of the doc to restart the search at the top. It is
this last function that IMO is causing the problem: it doesn't execute the
"start at top" function. At this point it seems to send the program into an
endless loop.
Discussion: I have been having the above described problem with Word2007
since I purchased it several months ago. I have re-installed the program
once, thinking perhaps the problem was a disk error. No luck, the problem
re-occurred as soon as I tested it. Here is how I induce the problem:
As mentioned above, I'm editing a 360 page document. I will be mid-way down
the document and need to search for a text string. If the target text string
is below the search initiation point, the "Find" function works without
error. However, if the target text string is higher up in the document,
which would require the search function to re-initiate the search at the top
of the document, the CPU immediately goes to 100% and spins in perpetuity.
It requires forcing Word2007 to quit.
I have now adopted the routine of starting all text searches from the top of
the document and this has eliminated the program lockups. Oddly, the problem
seems to exist only on a large document. The search function on a small
document of only several pages seems to work without error.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...8&dg=microsoft.public.word.application.errors