Thanks for the replies folks.

Greg your code is very cool! Clever how it steps through the different replacements. Often though, a report is built piece by piece over time. It would be laborious to to all of the replacements each time. To get a better idea of what I mean, here is a screenshot that shows the dialog which pops up when the boilerplate .docm is opened:


There's one radio button that changes three pronouns (he/him/his) and a couple of other things that minimizes the number of clicks needed.

There's a 22+ minute screencast [URL="https://www.youtube.com/watch?v=ebFeD5AKSpU&feature=youtu.be&fbclid=IwAR2e vyqMqAIbxwmIp4KnHygGqE2CSiM9J2KoVmHPFUhhjnuoj247nf mvqDs"]of it here. Though you guys probably get the gist of it just from the screenshot.

The file is here, if you want to look at the insides.

So by the time the dialog/form is closed, all of the replacements have been made. My current setup is that I just have tons of boilerplate statements in there, then I cull out the ones I don't want to use for a particular report. Instead, I'd like all of those statements stored as Quickparts. It would just be easier if all of the Quickparts had changes already made.

It's worth mentioning the "AutoText" might also work. I don't think AutoText allows tables though, which is unfortunate. I did try this code. But had problems with it.