#MICROSOFT WORD FIND AND REPLACE ALL HOW TO#
#MICROSOFT WORD FIND AND REPLACE ALL UPDATE#

The 'pre-fiddle' is to do a global find/replace across captions, replacing the em-dash ('^+') with some other string (e.g. If it does, then you'll need to do a pre- and post- 'fiddle' to ensure these em-dashes are not touched by the global replace above. NOTE: This presumes that em-dash does not appear in the caption text anywhere. Do a find/replace searching for special character 'em-dash' (^+) in style CAPTION, replacing with ' '.

FIGURE), select the other labels one by one and repeat this process. If you have other labels in use in the document (e.g. This will replace all separators in captions for the selected label in the CAPTION Window. Go to REFERENCES | INSERT CAPTION, then click on NUMBERING and replace the SEPARATOR '.' with 'EM-DASH'. To globally replace the separator '.' with ' ' (space) in such captions, take two steps:

This means these captions will have been (automatically) created in CAPTION style. It sounds like Beth may have created captions throughout the document using INSERT CAPTION (hence the presence of field codes). And this may not be quite what Beth was looking for.

#MICROSOFT WORD FIND AND REPLACE ALL UPDATE#

Update the field codes.Ĭoming in late on this, probably way too late for Beth (sorry Beth). Select-All and re-toggle the field codes. Add any further custom processing to the macro VBA. Hope I didn't complicate too much with the example >.It's usually better to go the macro route when finding fields because, as you say, the find algorithm that Word uses doesn't work the way you might hope with fields.īut if you know exactly what the fields contain, you can specify a search pattern that will probably work (however not in wildcard mode).įor example, if you want to look for figure number field pairs such as brackets. Action completed, affected files closed instead of remaining open as desired, but when I Ctrl+SHIFT+T to reopen them, the files brought to me were, let's say, l, k and g, instead of all five affected and only THEN the other three that were closed before the batch replacing. Then I needed to replace something in 5 other files (h, i, j, k, l). Here's a hypothetical scenario to describe what just happened to me: I had like 4 files (a, b, c, d) with 3 others previously closed (e, f, g) in history.

#MICROSOFT WORD FIND AND REPLACE ALL HOW TO#

I don't know how to explain but, it's like the replacement action takes place in the background or then it's like if it happens so fast that not all files in which a replacement had been performed end up being registered in the Recently Opened Files. While batching, all files are closed after VSCode finished work with each one of them. This may be an indirect question to this matter but, how do I keep the files I've performed a replacement on open after the procedure? Because, currently (to me), I Ctrl+SHIFT+H for the action but the files only remain open if I replace each occurrence manually, one entry after another (thus defeating the purpose of a batch replacement). Mm i think i may go for an extension! Start with the simple version! Then one see! Now clearly it's a matter of hands! (Time and will) ! Because that can go too as an extension! Why i will not be the one to do it !? My partner is already shouting! Focus Otherwise too a simple format! Straight forward! Not the most cool thing! But very helpful! Simply make it happen when no changes were made! Because a lot of times one hit replace all! And at the instant it's done! You know you made a mistake! You just want to cancel that! May be that's the most common scenario! (for this only! The implementation is straight forward! After a replace all! All the changed files listing (paths, id whatever) are saved in memory! to revert just do an undo file by file! If any of the file is modified before that! One can keep offering reverting the rest! And open the files with undo problem! And changed!ĮVen though using the stack and with walk through resolution is the cool thing! And require some work! For a cool handling! And simple walk through! In the worst cases! One can have even a walk thorugh file by file guiding to undo! (with undo, redo) (so it give the possiblity for copying ! undo! And then when all resolved! the button for undo replace all become enabled! (kind of like a conflict resolution in git walk through)! Simply guided and accessible!

If no change happened then cool! If some changes happened! Till they got canceled! (we are tracking the hassling block ! That give us the performance point! you don't go and check all! you track it on the go) Now for performance! One can optimize by listening to redo/undo stack of each concerned file! When the replace all undo is triggered! The mapping is used! We check for the whole list of files that were modified! And See if they were top in stack! If all are! And in the right stacked order for all file! Then it's doable and it can be handled! A solution would be to just use the normal undo stack! And to keep a mapping to what a replace all had as entries!

Microsoft word find and replace all