VBA reference changed version automatically

Question

I wrote some VBA in Excel 2013 which references Outlook and is now used on a virtual machine. My laptop was upgraded to Office 2016 last week, I made some changes in this tool and then it failed to run on the VM.

Turns out the VBA Outlook reference in the file changed to v16.0 (Office 2016) and so when the VM tried to run the code (on 2013), it couldn't find this reference.

There was also the generic Office reference which stayed as v15.0 though.

I haven't been able to find any documentation on this - is this standard behaviour and if so, any ideas on how I can make further changes to this file without the reference messing up every time?

Kostas K. · Accepted Answer · 2018-03-07 07:17:32Z

0

This is standard behaviour.

You need to move from Early to Late binding. Remove the Outlook reference in VBE and declare the outlook application as Object in code.

Dim olApp As Object
Set olApp = CreateObject("Outlook.Application")

Bare in mind by doing so you will lose intellisense and you may have to change some constants to their numeric values, e.g. olMailItem to 0.

Make sure you have Option Explicit at the very top of your module(s), as this will highlight compilation errors.

answered Mar 7, 2018 at 7:17

Kostas K.

8,5282 gold badges26 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

JakeyG Over a year ago

I have heard the terms "early binding" and "late binding" and never known what it related to or bothered to look it up - thanks! Problem solved and learned something new :-)

Collectives™ on Stack Overflow

VBA reference changed version automatically

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related