MSO.DLL Error.. How to programatically handle the MS Office objereferences between 2 Access versions

[stalk]

My current Access DB is using Microsoft Office 15.0 Object library. Some times if some one opens it in MS Office 16.0 Object library is missing error is showing up.
How can I handle this programmatically so that we will not see the missing Microsoft office 16.0 Object library when opened in MS office 2013 environment or vice-versa.

I know the easy way to fix it by going to tools- references and unchecking the missing link but I would like to do it programmatically.



Thanks in advance

[jwhite]

To be able to use the MSO Object Library across computers that use different versions, use Late Binding.
https://www.devhut.net/2016/11/08/vb...-late-binding/

Additionally, develop your application in a version of Access that equals the lowest version in use on workstations, so to reduce the chance of using features that aren't supported in prior versions.