Ensuring Office 2016 Access DB Libraries Work on older versions?

Question

I created an Access 2016 DB with forms and reports that run on a VBA back-end. After rigorous testing, I was ready to present it on a computer that had Access 2013. Within the first few seconds, I was hit with an error:

Compile Error:
Can't find project or library

... to which it redirected to me to a Date function I utilized in one of my forms. After removing it, the same error occurred, but now it was pointing to an Environ$("username") function.

I then figured out that this version of Access was missing some libraries containing these functions.

My question is: Is there a way to ensure that certain libraries stay active when exporting my database for others to use? Or would I manually have to do it on each computer I export the database to?

Answer 1

Hi,
Based on your description I'll move your question to the MSDN forum for Access developers:

https://social.msdn.microsoft.com/Forums/en-US/home?forum=accessdev

The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.

---

Regards,
Emi Zhang
TechNet Community Support

Please remember to mark the replies as answers if they helped.
If you have feedback for TechNet Subscriber Support, contact [e-mail].

Answer 2

I think you may benefit from reviewing http://www.devhut.net/2017/04/09/setting-up-an-ms-access-database/, specifically the section regarding support multiple versions.

You would also benefit from switching all your code over to Late Binding, you can learn more about it by reviewing http://www.devhut.net/2016/11/08/vba-early-binding-and-late-binding/.

---

Daniel Pineault, 2010-2017 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 3

In addition to the info from Daniel's link, if you are supporting both 32-bit and 64-bit Access then you will need to test the app in both.

If you use any third-party libraries (COM or ActiveX components) they will need to be deployed and registered. Those libraries that are installed with Windows usually are not a problem, but if that is a concern or issue then refer to the section in Daniel's article regarding early and late binding. Also, any 32-bit (DLL) libraries you use must have 64-bit versions in order to function under 64-bit Access. 

---

Paul ~~~~ Microsoft MVP (Visual Basic)

Answer 4

Just to add to Paul's post, if supporting 32 and 64 bit installations is a consideration for you, then review http://www.devhut.net/2017/04/13/access-x32-vs-x64-compatibility/

---

Daniel Pineault, 2010-2017 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net