Tinker,
You're so close to a possible answer and you don't even know it.
"I don't want to change the macro. It works fine."
Mmm... not exactly. It's pretty clear that the problem is the macro and not
Word because (according to you) this problem occurs _only_ when the macro
runs and not when Word is running by itself. Word is only as good at
whatever is driving it.
"The only thing the macro is doing is cutting and pasting. Word's respone
(sic) to cutting and pasting would be the same even if I did it manually."
Again, not exactly. In your original post you said that the problem occurs
after the macro performs around 40 such cut-n-paste operations. I would
imagine that it does this in a matter of moments, and you would struggle to
perform the same number of operations as quickly manually. Time is a factor
in these things, and manual operations are treated differently from
automated ones.
"How do I make Word stop generating the nag screen."
Word is generating this screen for a reason, and the way to make it stop is
to fix the cause of the nag screen. Just suppressing its display is not
enough. If you broke your leg you could be given medication that would stop
the pain but the leg wouldn't be healed, and if you walked on it... I'm sure
you see where this is going.
I can't give you an answer right now for the same reason that Graham didn't
give you one straight away either. I believe that Graham has asked you to
post the code from your third-party macro because he suspects that it is
inefficient but is unwilling to provide specific direction without first
seeing the code, and I agree with his position.
As for Pat Garard's little "rant" your response to it... well... what can I
say? I don't presume to speak for Pat, but we do all get frustrated with
posters from time to time - especially when the poster doesn't recognise the
importance or value of the answer they have been given. When I encounter
these situations I always try to follow Pat's advice and approach the
(secondary) problem with a 'Beginner's Mind' of my own. I ask myself what I
can do to shed sufficient light to allow the poster to see the value in the
answer provided. I can only hope that I have done this here.
So in summary, it would appear that the problem is caused by the third-party
macro. In this instance I would recommend that you contact the vendor of
this macro. If you get no joy through this route, post the code and we'll
see what we can do.
--
Cheers!
Gordon Bentley-Mix
Word MVP
Uninvited email contact will be marked as SPAM and ignored. Please post all
follow-ups to the newsgroup.