Fascinating! This certainly isn't normal Word behaviour.
If this happens so rapidly that you can't type anything after dismissing one
prompt before seeing another then it seems unlikely that it is something you
are accidentally triggering. The implication is that some software is
running behind the scenes. Anything as insistent as this I would consider
malware of some sort (and I do consider much 'genuine' software to behave so
badly as to be so classified) but it may be an addin deliberately designed
to force you to save your work regularly to stop you losing it. If you start
Word in safe mode (press and hold Ctrl while Word starts) do you still get
the problem?
--
Enjoy,
Tony
LJ said:
Hi Doug.
I am so glad that "Student with Word" has given me a place to start. I'm
sure this problem is not being caused by inadvertent keyboard commands; I
tried typing "the quick brown fox" a few times to check out this out. "Save
as" popped up indiscriminately. Also, I am using a computer that is
only
two
months old; it came with Windows and Office loaded, and there are no Addins
yet (that I can find). I also checked for macros...not one yet.
Perhaps I can supply a little more info. that might be helpful.
1. This problem is not confined to Word. It also happens when I am working
with Excel and Outlook. I haven't tested it out in PPoint, Access, or
Publisher.
2. It doesn't start happening right away, but once it starts happening it
speeds up (becomes more "insistent"). At first, the popups are 5-10 seconds
apart, and it doesn't matter if I "cancel" or "save as," they begin speeding
up until they are reocurring so fast that I can not type one letter of text
between them.
3. The only way to continue working is to reboot the computer. Then, after
15 or 20 minutes, the cycle starts all over again.
This is so aggravating that it has taken all of the pleasure out of having
the great new laptop that I have waited so long to be able to purchase. I
appreciate your response to Student with Word and am hoping that you will
hang in there with us until we can figure out how to correct this.
Thank you!
LJ