Microsoft word Object Early/Late Binding

[rjtaylor]

I write code at home and work. Home computer needs Microsoft Word 15.0 Object Library. When I program at work the reference changes to Microsoft Word 16.0 Object Library. Then the program hangs when back at home.
After searching I learned that I should use Late binding. The problem is that in late binding I get an error when setting the footer but it goes away with the reference set.

Dim myRange

'Early Binding
Dim wApp As Word.Application
Dim wDoc As Word.Document

Set wApp = CreateObject("Word.application")
Set wDoc = wApp.Documents.Add

'Late Binding
'Dim wApp As Object
'Dim wDoc As Object
'
'Set wApp = CreateObject("Word.Application")
'Set wDoc = wApp.Documents.Add

 

[Domenic]

When using late binding, you need to use values instead of constants. For example, here are the corresponding values for the WdHeaderFooterIndex enumeration...

[U]Constants ===> Values
[/U]
wdHeaderFooterEvenPages ===> 3 
wdHeaderFooterFirstPage ===> 2
wdHeaderFooterPrimary ==> 1

Hope this helps!

 

[Macropod]

When using early binding, you should always compile the project on the earliest Office version you're supporting.

If that's not an option, you can develop code using early binding, then convert to late binding for deployment. As Domenic said, you need to use values instead of constants when using late binding. That said, you can continue to use the early binding names in your code if you declare them beforehand. Taking his WdHeaderFooterIndex values as an example, you might insert:
Const wdHeaderFooterPrimary As Long = 1
Const wdHeaderFooterFirstPage As Long = 2
Const wdHeaderFooterEvenPages As Long = 3
at the top of your code. In the body of your code, you could then keep using those constant names with late binding just as you'd been doing with the early binding.

 

[rjtaylor]

Thank you both this will help