Access Runtime 2016

Discussion in 'Access' started by dwolovi, Oct 18, 2017.

  1. dwolovi

    dwolovi

    Joined:
    Oct 18, 2017
    Messages:
    1
    Likes Received:
    0
    Runtime 2016 does not work, and neither does 2013. Both return a message that the database is in an unrecognized format. I updated the app a week ago and the new accde is causing the problem. I have an accde file created in December 2016 that does work with runtime 2010 and 2013. From reading various websites, it looks like there is an incompatibility with CTR. I really don't care about CTR or non-CTR. I have an app created originally in Access 2010 that I installed using Sagekey in other machines. Everything worked fine, even as Office 365 upgraded my development machine over the last 3 or 4 years. It used to be pretty straightforward to create an executable (accde) and install it on another machine with a runtime. Apparently that can't be done anymore.
     
    dwolovi, Oct 18, 2017
    #1
    1. Advertisements

  2. dwolovi

    HiTechCoach

    Joined:
    Dec 7, 2011
    Messages:
    16
    Likes Received:
    0
    It is definitely still possible to use the Access Runtime. I have 1000+ customer workstations running Access 2010, 2013, and 2016 runtime versions with my accde compiled in Access 2010.

    Did you get this resolved?
     
    HiTechCoach, Nov 4, 2018
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.