VBA compile error in 2013

[dpebble62]

I am a developer supporting a Front End/ Back End MsAccess database solution. When I add functionality to the Front End and recompile, everything works fine for me.

But when my users download the new Front End, they always start with a compile error, requiring them to use "Tools | References", where they find "Visual Basic for Applications ticked - but STILL need to click BROWSE then OK for this library. Then they recompile (Debug | Compile) and all is well.

The above never happened while everyone was on Office 2010. But the move to 2013 has meant this happens to all my users, who are NOT sufficiently IT literate to be able to do this fix themselves.

Any idea how to ensure that new versions of the Front End will run on users' PCs without them needing to know how to recompile?

Many thanks for your help.

 

[Ranman256]

I get this a lot. Certain users dont have the same drivers/versions as you.
And you cant program it because the app crashes once it cant find the correct version.

you MUST make the settings on THAT PC. (it stinks)

 

[Gasman]

Could it be done via the registry?

 

[Ranman256]

you can copy and paste the control to the target computer.
As long as they have the file, it works.

 

[Minty]

Is this not a early/late binding issue?
The other (cheaper) option is to not install access full version but to install the 2010 access runtime and use that instead.

 

[dpebble62]

Thanks for your responses. But it's not a control - it's the main VBA library itself! And the path is the same on my users' PCs as mine. Yes, it'll almost certainly be a registry key issue. Just need to locate it, then I can supply a .reg file for users to double-click