Ensuring Office 2016 Access DB Libraries Work on older versions? RRS feed

  • 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?

    Monday, September 11, 2017 7:32 PM

All replies