dotX | Simple & Beautiful Jekyll theme | Theme library

The problem is you assigned the built in function open as a variable to PhotoImage. Now, when you call open, it fetches the value of the open variable because it's assigned a value. This will cause the error. That is why you should never use built-in functions as a variable. You can use open_img or anything that is not a keyword, a built-in function, a function you have defined.

open = Photos(nm + '\open.png', 10, 10), this is a mistake

open_img = Photos(nm + '\open.png', 10, 10) This would work .

Then updated the menu to fileMenu.add_command(label='Open...', command=openfiles, image=open_img, compound='left')

The main problem you have it that Word throws a runtime error if you try to unprotect a document that has no protection. Additionally, I would suggest you remove the On Error GoTo ErrHandler-statement (as it's better to let the VBA runtime to show you the exact statement where an error occurred).

Do a simple change in your unprotect routine: Check first if the doc has a protection. I would suggest that you pass the doc as parameter so you don't rely on ActiveDocument (you need to change the call to Call RemovePwd(doc) (or simply RemovePwd doc which means exactly the same)

When you create your document with Editor like MS Word it could add some containers, which wrap your paragraph, I'd suggest you check xml which generated. To do that, you can simply rename .docx to .zip and open that archive.

Inside you will found files like that

You will need to open word/document.xml with any text editor and see, if there and it is direct child of . If it is not direct, use descendants method.

The security policy of Firefox is different from chrome and edge. It may be because you open the html file directly on local machine. This will cause Chrome and Edge to be unable to directly access local resources. If you want to run in chrome and edge, please create a web server to run this file.

Be similar to this question.

And you can make chrome have permission to access the file. link

You will want to use the .Add method instead of .Open and specify the Template argument.

I haven’t run your code, but as far as I can see, this code would probably fail even without the formcount loop in the situation where you have more than one MERGEFIELD field because you close doc As soon as you have processed such a field, and yet the foreach loop is processing each Field in doc.Fields.

Even if that foreach loop terminates gracefully, in the next iteration of the formCount loop you are using doc.Activate(), but doc has closed so that will fail.

So I suggest that the main thing to do is consider which documents need to be open at which point for the process to work.

Some observations (not necessarily to do with your primary question)

• where is myInt set?
• is having a formCount++ loop and using formCount++ within the loop for every MERGEFIELD in doc Really your intention?
• you might be better off testing field.Type() when filtering MAILMERGE fields rather than matching the text, at least if such fields can be set up by end users
• when you process collections in Word and you are either adding or deleting members of the collection, you sometimes have to consider using a loop that starts with last member of the collection and works back towards the beginning. Not sure you need to do that in this case but since you may be “deleting” when you do your field.Select then Typetext, please bear that in mind
• It may seem like a complication when you are mainly trying to sketch out the logic of your loops, but I generally find it very helpful to start using try...catch...finally blocks sooner rather than later during development.

As @BigBen pointed out you have some commands inside your loop that should be outside it. I have rewritten your code to show you how you can some additional improvements that will help optimize your code.

VBA code runs more quickly if you avoid selecting things. This applies equally to Excel and Word. Both applications have Range objects that can be used in place of Selection.

You also have an undeclared variable in your code, Row, so you should add that to your variable declarations, (preferably using a different name though as Row is an object in Excel and confusion can occur when variables have the same name). You can avoid these issues by adding Option Explicit at the top of the code module. This will prevent your code from compiling when you have undeclared variables. To add this automatically to new modules open the VBE and go to Tools | Options. In the Options dialog ensure that Require Variable Declaration is checked.

On the whole though it's not a bad start for someone new to VBA.

It looks as though you are using late binding which means that you cannot use constants and enums from the Word object library, e.g. wdAllowOnlyFormFields. So your code should be: