VBA add-in no longer works in Word 2016 - macro error

[paulkaye]

Several years ago, while using Word 2007, I began regularly using a plugin for Word called "VBA Find and Replace". It could well have been one of you guys that helped me with it. Recently I switched to Word 2016, and although the add-in appears in an "add-ins" menu in the Word menu bar, when I click on it I receive the following error:

The macro can't be found or has been disabled because of your macro security settings

If I click on "show help", the following text is displayed:

This message can appear if:


⦁ The macro was deleted from the template.
⦁ The template was not loaded or referenced in the Templates and Add-ins command.
⦁ The macro was turned off by the macro security settings of your system.
If the macro security settings are not allowing the macro to run, you should confirm the origin of the macro to be sure that it can be trusted (contact the developer or the source for the macro). You can then temporarily enable all macros by using the following procedure.
1. Click the File tab, click Options, click Trust Center, and then click Trust Center settings.
2. Click Macro Settings.
3. Under Macro Settings, click Enable all macros.
NOTE: Be sure to change this option back to its original setting after you have run the macro.
If the macro is not accessible because the template is not loaded, click the File tab, click Options, and then click Add-Ins. At the bottom of the Add-Ins pane, select Templates from the Manage drop down list, and then click Go. In the Templates and Add-ins dialog box, click either Attach or Add. If the macro is not in the template, you may need to copy the macro from one template to another. Click the Organizer button at the bottom of the Templates and Add-ins dialog box to start the Organizer utility.

As far as I can tell, everything is in its correct place, and macros are enabled. I simply cannot work out what's going on. I found very few posts on the web, and none of them seem to answer my question.
Any help would be very appreciated.

[gmayor]

You will also get that error if there is an error in the code that makes it incompatible with Word 2016. As you have not shared the code it is not possible to form a judgement about what is causing the error. One possibility is that you have installed the 64 bit of Office 64 and the code is not compatible with that version.

As the add-in is concerned with find and replace, you could try instead http://www.gmayor.com/document_batch_processes.htm which includes find and replace options and which is compatible with Word 2016 and should be with the 64 bit version.

[paulkaye]

Thanks, Graham.
The add-in that I'm using is at http://gregmaxey.com/word_tip_pages/...d_replace.html

I suspect that it's an incompatibility issue.

Your batch processes add-in looks interesting, and I'll give it a go when I have a little time. It looks like it might also allow me to do some other things that I've wanted to be able to do for a while.

Thanks.

(If anyone can figure out a way to make the Greg Maxey add-in work in Word 2016, I'd still be very grateful.)

[gmayor]

Greg's add-in should work. Why don't you ask him? He has a contact page on his web site.

[paulkaye]

Hi Graham,
So I decided to give your add-in a try. My first observation is that it would be nice to be able to select a table of find-replace pairs each time, rather than having to edit the actual add-in template. (That's how Greg's add-in [used to] work.)
So far I've only run your add-in once, and Word (2016) stopped responding. I'll try again, but I wonder if it's anything to do with the WC and WWO columns in the add-in table. Your website seems to indicate that for each find-replace pair, one of these columns must have a Y in it. But what if I don't want to use wildcards nor "whole word only"?
Paul

[paulkaye]

Graham - I've PM'd my find-replace pairs to you, in case they're relevant to this issue.

[paulkaye]

Argh - it turns out that I *did* need wildcards active in order for the add-in to work for my find-replace pairs. Now that I've identified that, the gmayor add-in worked perfectly, as far as I can tell. But I wonder what caused Word to freeze the first time I ran it. Are there any document elements that could cause that? For example, comments?