Windows Installer when file opens

[hotabae]

Hello everyone,

I have been working on a Excel/Vba project for a few months, but recently, this issue cropped up.

When my file is opened on other computers, Windows Installer runs (right after clicking 'enable macros'). This isn't a huge problem so far, but I'd like to understand what is happening.

This is happening to people who use Excel frequently, so it seems tied to my file specifically. I'm not sure what could be causing it.

- I did run the "Online Repair" tool fairly close to when I became aware of the issue.
- The other users are on the same network. One had Excel 2013, and one had 2016. (I am on 2013).
- The guy with 2013 has a "professional plus" version, while mine is standard.
- I haven't added any Add-Ons to my file.
- Other than that, my code is fairly basic. I do use a few, additional object reference libraries.

Any thoughts on why this could be happening, or even what is happening?

Thanks!

 

[RoryA]

I do use a few, additional object reference libraries.

Which ones?

 

[hotabae]

All of these references are checked:

Visual Basic for Applications
Microsoft Excel 15.0 Object Library
OLE Automation
Microsoft Office 15.0 Object Library
Microsoft Forms 2.0 Object Library
Microsoft VBScript Regular Expressions 5.5
Ref Edit Control

 

[RoryA]

Do the other users use VBA normally?

 

[hotabae]

Do the other users use VBA normally?

One of them might have a few years ago, but the other, no.

Edit: They have both recently (2 months ago or so) run earlier versions of my code without this issue.

 

[RoryA]

With the same references? This kind of thing is often caused by different versions of components (my first guess would be the RefEdit control).

 

[hotabae]

The only new reference since they ran it last time is "Ref Edit Control".

 

[RoryA]

I think you posted at the same time I was editing my last post!

Try removing the reference for the refedit. It should work without the reference.

 

[hotabae]

I have removed the reference going forward. I'm pretty sure it was only there from testing something I saw on this board, I wasn't utilizing it anyway.

I don't have the ability to test it yet, but based on some searching around, it seems like it'll probably be the solution.

Thanks for your help, I'll report back eventually when I see the results.