Quote:
Originally Posted by Guessed
Cendrinne
Edit: I think the wdFindStop could be a problem as the range may collapse as you progress through the code. It is possibly better to use wdFindContinue if you are encountering issues.
Another tip is to not be so liberal with your use of Application.ScreenUpdating = False
It is better to not do that until your code is fully debugged as it stops you from seeing what is going on as your macro runs and makes life difficult if the code fails at any point before you turn it on again.
|
First paragraph above, I always thought wdFind Stop was to have it START as of the cursor till the end of the document or range. Or else it will start again from the beginning of the document or range. Is that thinking wrong?
Second paragraph above, thank you, never thought of that.
Sorry for my tardy response, I am so busy, and put in so much hours and efforts of my time during the week, that I take a look of my former postings on the later part on the weekend.
Thank you for your insights and Scripts. I can't wait to try them and especially, ......get explanations as to why I should use Continue vs Stop
Cendrinne
04-18-2021, 12:19 PM
Responding to your Stop vs Continue comment....
Similar Threads
Splitting Tables containing Merged Cells
Windows 10 
Office 2019
Threaded Mode